A method and system for integrating content viewing and communication in immersive social centre session

ABSTRACT

A method and system for establishing the ISC session among one or more communication devices for a content viewing and/or a communication to enable integration of the content viewing and the communication is provided. The integration or convergence of the content viewing and the communication provides an immersive user experience to one or more ISC users in the ISC environment participating in the ISC session including a self ISC session, a one to one ISC session or a group ISC session. The method allows an initiator ISC client to append one or more first parameters in a first SIP INVITE for the content viewing and one or more second parameters in a second SIP INVITE for the communication. The common appended parameters such as an ISCConvergenceID indicate the media function and the communication function to integrate the communication with respect to the content viewing.

TECHNICAL FIELD

The present invention relates to mobile communications and moreparticularly relates to enabling multimedia service on mobile devices byintegrating content viewing and communication.

BACKGROUND ART

Rapid developments in mobile communication technology provide ubiquitousnetwork connectivity. With evolving communication devices such as smartphones; demand for content viewing on the communication devices isgrowing exponentially. In today's highly competitive telecommunicationindustry, providing rich and satisfying user experience is a challengingtask for network operators and service providers. Thus, serviceproviders are keen on focusing their efforts towards providing valueadded services with the content viewing service provided to a user onhis/her mobile communication device. Convergence of content viewing andcommunication enables the service provider to provide an immersiveexperience to the user. For example, chatting with a group of friendswhile the group enjoys watching same match live on their respectivesmart phones.

Existing methods provide standard and non-standard enablers fordistribution of multimedia for content viewing and communication.However, content viewing and communication are mostly deployed as silosand are mostly based on interfaces independent of each other. Thisindependent deployment is a hurdle for providing integration of contentviewing and communication. Currently, whenever the user desires tocommunicate with other users in context of the content being viewed onhis/her mobile communication device; generally, the user explicitlyprovides the context of the content being viewed. This fails to providean immersive feeling in context of the content being viewedsimultaneously by multiple users on their respective communicationdevices.

However, the service provider delivering the content to the user isaware of the user context with reference to content being viewed by theuser. Currently, Open Mobile Alliance (OMA) has identified requirementsof the Immersive Social Centre (ISC) enabler to include requirements forenhancing user experience with value added features to provide immersive(being their-being with) experience. These value added features includeenabling multiple communication devices identified as a group tosimultaneously organize a content viewing session and a communicationsession to enable integration of content viewing and communicationsession in the group with reference to the content being viewed.

Providing efficient methods to meet the requirements of the ISC enablerfor integration of content viewing and communication to enhance userexperience and effectively improve service penetrations will beappreciated.

DISCLOSURE OF INVENTION Technical Problem

However, the service provider delivering the content to the user isaware of the user context with reference to content being viewed by theuser. Currently, Open Mobile Alliance (OMA) has identified requirementsof the Immersive Social Centre (ISC) enabler to include requirements forenhancing user experience with value added features to provide immersive(being their-being with) experience. These value added features includeenabling multiple communication devices identified as a group tosimultaneously organize a content viewing session and a communicationsession to enable integration of content viewing and communicationsession in the group with reference to the content being viewed.

Solution to Problem

The principal object of the embodiments herein is to provide a methodand system to establish an Immersive Social Centre (ISC) session forcontent viewing and/or communication based on ISC architecture for apersonal ISC session, a one to one ISC session or a group ISC session.

Another object of the invention is to provide a method that enablesintegration of content viewing and/or communication in the establishedISC session.

Accordingly the invention provides a method for establishing anImmersive Social Centre (ISC) session by an ISC server, wherein themethod comprises receiving a first Session Initiation Protocol (SIP)INVITE including at least one first parameter from an initiator ISCclient by a media function in the ISC server. The first SIP INVITE isfor initiating the ISC session for a content viewing when the initiatorISC client receives a request for establishing the ISC session for thecontent viewing, wherein the at least one first parameter comprises aheader field, at least one element in a Multipurpose Internet MailExtensions (MIME) body and a Session Description Protocol (SDP). Furtherthe initiated ISC session for the content viewing is identified by anISC session identifier sent in the header field of the at least onefirst parameter. The method further comprises receiving a second SIPINVITE comprising at least one second parameter from the initiator ISCclient by a communication function in the ISC server. The second SIPINVITE is for initiating the ISC session for a communication when theinitiator ISC client receives the request for establishing the ISCsession for the communication. Further, a communication sessionidentifier in the second SIP INVITE is assigned with a value of the ISCConvergence ID for integrating the communication with the contentviewing in the ISC session and the at least one second parametercomprises the header field, the at least one element in the MIME bodyand the SDP. Furthermore, the method comprises establishing the ISCsession for the content viewing by the media function based on the ISCsession identifier received in the first SIP invite, the element in theMIME body and the SDP in the first SIP INVITE. Furthermore, the methodcomprises establishing the ISC session for the communication by thecommunication function based on the communication session identifierreceived in the second SIP invite assigned with the value of the ISCsession identifier, the SDP and the element in the MIME body of thesecond SIP INVITE. The communication session identifier identifies thecommunication in the ISC session.

Accordingly the invention provides a method for initiating an ImmersiveSocial Centre (ISC) session by an initiator ISC client, wherein themethod comprises receiving a request to initiate the ISC session for atleast one of content viewing and communication. Further, the methodcomprises generating and sending a first Session Initiation Protocol(SIP) INVITE including at least one first parameter to a media functionin the ISC server for initiating the ISC session for the content viewingwhen the received request is for the content viewing. Further, the atleast one first parameter comprises an header field, at least oneelement in a Multipurpose Internet Mail Extensions (MIME) body and aSession Description Protocol (SDP) and the initiated ISC session for thecontent viewing is identified by an ISC session identifier sent in theheader field of the at least one first parameter. Further, the methodcomprises generating and sending a second SIP INVITE comprising at leastone second parameter to a communication function in the ISC server toinitiate the ISC session for the communication when the received requestis for the communication. Further, a communication session identifier inthe second SIP INVITE is assigned with a value of the ISC sessionidentifier for integrating the communication with the content viewingand the at least one second parameter comprises the header field, the atleast one element in the MIME body and the SDP. Further, the methodcomprises participating in the ISC session for content viewing after themedia function establishes the ISC session based on the ISC sessionidentifier, the element in the MIME body and the SDP in the first SIPINVITE. Furthermore, the method comprises participating in the ISCsession for communication after the communication function establishesthe ISC session for the communication based on the communication sessionidentifier assigned with the value of the ISC session identifier, theSDP and the element in the MIME body of the second SIP INVITE.

Accordingly the invention provides a method for participating in anImmersive Social Centre (ISC) session by an recipient ISC client,wherein the method comprises receiving at least one of a forwarded firstSIP INVITE from a media function of a ISC server and a forwarded secondSIP invite from a communication function of the ISC server forparticipating in an ISC session initiated by an initiator ISC client.Further the ISC session is one of a one to one ISC session and a groupISC session initiated by an initiator ISC client. Further, the methodcomprises determining whether the ISC session is for at least one of thecontent viewing and the communication based on a value of a ISCSessionType received in at least one of a forwarded first SIP INVITEfrom the media function of a ISC server and a forwarded second SIPINVITE received from the communication function of the ISC server.Further, the method comprises notifying an ISC user of the recipient ISCclient of invitation for the initiated ISC session based on thedetermined value of the ISC SessionType. Furthermore, the methodcomprises sending response to the media function and the communicationfunction indicating participation in the ISC session based on input fromthe ISC user.

Accordingly the invention provides a system for establishing anImmersive Social Centre (ISC) session, wherein the system comprises anISC server, an initiator ISC client, and plurality of recipient ISCclients. Further the initiator ISC client configured to receive arequest to initiate the ISC session for at least one of content viewingand communication. Further, the initiator ISC client is configuredgenerate and send a first Session Initiation Protocol (SIP) INVITEincluding at least one first parameter to a media function in the ISCserver for initiating the ISC session for the content viewing when thereceived request is for the content viewing. Further, the at least onefirst parameter comprises an header field, at least one element in aMultipurpose Internet Mail Extensions (MIME) body and a SessionDescription Protocol (SDP) and wherein the initiated ISC session for thecontent viewing is identified by an ISC session identifier sent in theheader field of the at least one first parameter. Further the initiatorISC client is configured to generate and send a second SIP INVITEcomprising at least one second parameter to a communication function inthe ISC server to initiate the ISC session for the communication whenthe received request is for the communication. Further, a communicationsession identifier in the second SIP INVITE is assigned with a value ofthe ISC session identifier for integrating the communication with thecontent viewing and the at least one second parameter comprises theheader field, the at least one element in the MIME body and the SDP.Further the media function is configured to receive the first SIP INVITEsent by the initiator ISC client and establish the ISC session for thecontent viewing based on received the ISC session identifier, theelement in the MIME body and the SDP in the first SIP INVITE. Further,the communication function is configured to receive the second SIPINVITE sent by the initiator ISC client and establish the ISC sessionfor the communication based on received communication session identifierassigned with the value of the ISC session identifier, the SDP and theelement in the MIME body of the second SIP INVITE.

Accordingly, the invention provides a computer program productcomprising computer executable program code recorded on a computerreadable non-transitory storage medium, the computer executable programcode when executed, causing the actions including receiving a firstSession Initiation Protocol (SIP) INVITE including at least one firstparameter from an initiator ISC client by a media function in the ISCserver for initiating the ISC session for a content viewing when theinitiator ISC client receives a request for establishing the ISC sessionfor the content viewing. The at least one first parameter comprises aheader field, at least one element in a Multipurpose Internet MailExtensions (MIME) body and a Session Description Protocol (SDP). Theinitiated ISC session for the content viewing is identified by an ISCsession identifier sent in the header field of the at least one firstparameter. Further the computer program product is configured to receivea second SIP INVITE comprising at least one second parameter from theinitiator ISC client by a communication function in the ISC server toinitiate the ISC session for a communication when the initiator ISCclient receives the request for establishing the ISC session for thecommunication and a communication session identifier in the second SIPINVITE is assigned with a value of the ISC session identifier forintegrating the communication with the content viewing in the ISCsession. The at least one second parameter comprises the header field,the at least one element in the MIME body and the SDP. Further, thecomputer program product is configured to establish the ISC session forthe content viewing by the media function based on the ISC sessionidentifier received in the first SIP invite, the element in the MIMEbody and the SDP in the first SIP INVITE. Furthermore, the computerprogram product is configured to establish the ISC session for thecommunication by the communication function based on the communicationsession identifier received in the second SIP invite assigned with thevalue of the ISC session identifier. Further, the ISC session isestablished based on the SDP and the element in the MIME body of thesecond SIP INVITE, wherein the communication session identifieridentifies the communication.

These and other aspects of the embodiments herein will be betterappreciated and understood when considered in conjunction with thefollowing description and the accompanying drawings. It should beunderstood, however, that the following descriptions, while indicatingpreferred embodiments and numerous specific details thereof, are givenby way of illustration and not of limitation. Many changes andmodifications may be made within the scope of the embodiments hereinwithout departing from the spirit thereof, and the embodiments hereininclude all such modifications.

BRIEF DESCRIPTION OF DRAWINGS

This invention is illustrated in the accompanying drawings, throughoutwhich like reference letters indicate corresponding parts in the variousfigures. The embodiments herein will be better understood from thefollowing description with reference to the drawings, in which:

FIG. 1 illustrates an Immersive Social Centre (ISC) architecture forestablishing an ISC session, according to embodiments as disclosedherein;

FIG. 2 is an example illustration of User Interface on communicationdevices participating in the ISC session, according to embodiments asdisclosed herein;

FIG. 3 illustrates modules of a communication device for establishingthe ISC session, according to embodiments as disclosed herein;

FIG. 4 illustrates modules of an ISC server for establishing the ISCsession initiated by the communication device, according to embodimentsas disclosed herein;

FIG. 5 is a flow diagram illustrating a method for establishing an ISCsession for content viewing and/or communication, according toembodiments as disclosed herein;

FIG. 6 is an example sequence diagram illustrating establishing of apersonal ISC session for content viewing when contents are available toa ISC client of the communication device as unicast content and changingof the content being viewed is performed through a Session InitiationProtocol (SIP) re-INVITE, according to embodiments as disclosed herein;

FIG. 7 is an example sequence diagram illustrating establishing of thepersonal ISC session for content viewing when contents are available tothe ISC client as multicast content and changing of the content beingviewed is performed through the SIP re-INVITE, according to embodimentsas disclosed herein;

FIG. 8 is an example sequence diagram illustrating establishing of thepersonal ISC session for content viewing when contents are available tothe ISC client as unicast content and Real Time Streaming Protocol(RTSP) controls are provided to a user of the mobile communicationdevice, according to embodiments as disclosed herein;

FIG. 9 is an example sequence diagram illustrating initiation of a oneto one ISC session for content viewing and communication, according toembodiments as disclosed herein;

FIG. 10a,b is an example sequence diagram illustrating establishing ofthe one to one ISC session for content viewing and communication whencontents are available to ISC clients of the mobile communicationdevices participating in the one to one ISC session as unicast contentand changing of the content being viewed is performed through the SIPre-INVITE, according to embodiments as disclosed herein;

FIG. 11a,b is an example sequence diagram illustrating establishing ofthe one to one ISC session for content viewing and communication whencontents are available to the ISC clients as multicast and changing ofthe content being viewed is performed through the SIP re-INVITE,according to embodiments as disclosed herein;

FIG. 12 is an example sequence diagram illustrating establishing of theone to one ISC session for content viewing and communication whencontents are available to the ISC clients as unicast content and RTSPcontrols are provided to the user, according to embodiments as disclosedherein;

FIG. 13 is an example sequence diagram illustrating establishing of theone to one ISC session for content viewing and communication when amedia function and a communication function are integrated in a ISCserver, according to embodiments as disclosed herein;

FIG. 14 is an example sequence diagram illustrating establishing of agroup ISC session among a pre-defined group for content viewing andcommunication when contents are available to the ISC clients of thepre-defined group as unicast content, according to embodiments asdisclosed herein;

FIG. 15 is an example sequence diagram illustrating changing the contentbeing viewed by the pre-defined group through the SIP re-INVITE whencontents are available to the ISC clients of the as unicast contentduring the group ISC session, according to embodiments as disclosedherein;

FIG. 16 is an example sequence diagram illustrating establishing of thegroup ISC session among the pre-defined group for content viewing andcommunication when contents are available to the ISC clients in thepre-defined group as multicast, according to embodiments as disclosedherein;

FIG. 17 is an example sequence diagram illustrating changing the contentbeing viewed by the pre-defined group through the SIP re-INVITE whencontents are available to the ISC clients of the pre-defined group asmulticast content during the group ISC session, according to embodimentsas disclosed herein;

FIG. 18a,b is an example sequence diagram illustrating establishing ofthe group ISC session for content viewing and communication whencontents are available to the ISC clients as unicast and RTSP controlsare provided to the user, according to embodiments as disclosed herein;

FIG. 19 illustrates an example sequence diagram for forming an ad-hocISC group to establish the group ISC session when contents available tothe ad-hoc group is unicast, according to embodiments as disclosedherein;

FIG. 20 illustrates an example sequence diagram for extending anestablished one to one ISC session to the group ISC session, accordingto embodiments as disclosed herein;

FIG. 21 illustrates an example sequence diagram for establishing groupISC session for content viewing and communication when the mediafunction and the communication function are integrated in the ISCserver, according to embodiments as disclosed herein; and

FIG. 22 illustrates a computing environment implementing a method andsystem for establishing the ISC session for integrating content viewingand communication, according to embodiments as disclosed herein.

BEST MODE FOR CARRYING OUT THE INVENTION

The embodiments herein and the various features and advantageous detailsthereof are explained more fully with reference to the non-limitingembodiments that are illustrated in the accompanying drawings anddetailed in the following description. Descriptions of well-knowncomponents and processing techniques are omitted so as to notunnecessarily obscure the embodiments herein. The examples used hereinare intended merely to facilitate an understanding of ways in which theembodiments herein can be practiced and to further enable those of skillin the art to practice the embodiments herein. Accordingly, the examplesshould not be construed as limiting the scope of the embodiments herein.

Prior to describing the embodiments in detail, it is useful to providedefinitions for key terms and concepts used herein. Unless definedotherwise, all technical and scientific terms used herein have the samemeaning as commonly understood by a person having ordinary skill in theart to which this invention belongs.

Initiator Immersive Social Centre (ISC) client: Refers to an ISC clienton a communication device that initiates an ISC session. The ISC sessionis initiated by an initiator ISC client on receiving a request from auser (ISC user) and receiving ISC service from an ISC enabler providedby an ISC environment. The ISC session can be a personal ISC session, aone to one ISC session or a group ISC session. Further, the initiatorISC client is also called the originating client.

Recipient ISC client: Refers to an ISC client on another communicationdevice of another ISC user participating in the ISC session. The ISCsession referred here can be one to one ISC session or a group ISCsession initiated by the initiator IS client. Here, group ISC sessionmay involve a session established among multiple ISC clients forming thegroup. Further, the recipient ISC client is also called the terminatingclient.

The embodiments herein achieve a method and system for establishing theISC session among one or more communication devices for content viewingand/or a communication to enable integration of the content viewing andthe communication in an ISC environment. The integration or convergenceof the content viewing and the communication provides an immersive userexperience to the ISC users in the ISC environment participating in theISC session.

The ISC session can be a personal ISC session, a one to one ISC sessionor the group ISC session managed by an ISC server in the ISC enabler. Apersonal ISC session also called a self ISC session is initiated by aninitiator ISC client for content viewing. A one to one ISC session is asession between the initiator ISC client and a recipient ISC clientselected from a plurality of recipient ISC clients in the ISCenvironment. A group ISC session is among group members including theinitiator ISC client and plurality of recipient ISC clients in the ISCenvironment.

The method allows a media function in the ISC server to manage thecontent viewing of ISC session and allows a communication function ofthe ISC server to manage the communication of the ISC session usingSession Initiation Protocol (SIP). The method allows the initiator ISCclient to append one or more first parameters in a first SIP INVITE forthe content viewing and one or more second parameters in a second SIPINVITE for the communication.

In an embodiment, the initiator ISC client internally communicates withan initiator communication client (Converge IP Messaging (CPM) client)to generate and send the second SIP INVITE for communication towardscommunication function. The appended parameters such as an ISC sessionidentifier which is an ISC Convergence ID common to both the first SIPINVITE and the second SIP INVITE indicate the media function and thecommunication function to establish the communication with respect tothe content viewing.

The first SIP INVITE and the second SIP INVITE are forwarded to one ormore recipient ISC clients based on whether the ISC session request isfor the one to one ISC session or the group ISC session. The appendedparameter such as an ISC SessionType (SessionType) to the first SIPINVITE and second SIP INVITE indicate the recipient ISC clients whetherthe request received for ISC session establishment is for either or boththe content viewing and the communication.

In an embodiment, the recipient ISC client internally communicates witha recipient CPM client for handling the second SIP INVITE, forwarded bythe communication function. The integration provided by the methodenables the communication function to establish the communication withreference to the content being viewed during the content viewingestablished by the media function.

Further, the method allows the ISC server to manage the request receivedfrom the initiator ISC client for initiation of the ISC group sessionamong a pre-defined ISC group or an ad-hoc ISC group formed by theinitiator ISC client.

In an embodiment, the method allows the ISC server to manage the requestfrom the initiator ISC client for change of content being viewed duringthe established ISC session. The method allows the ISC server to managerequest from recipients ISC client participating in an established ISCsession to leave the established ISC session.

In an embodiment, the method allows the initiator ISC client to send arequest for adding or terminating the group members to or from anestablished group ISC session. Furthermore, the method allows theinitiator ISC client to send a request for extending an established oneto one ISC session to the group ISC session.

However, the communication function refers to the CPM enablerserver-side functional component, thus throughout the description theterms communication function and CPM are used interchangeably.

In an embodiment the communication device can be a smart phone, atablet, a personal digital assistant, a palmtop, a laptop and any othercommunication device capable handling ISC session.

Referring now to the drawings that include FIGS. 1 through 22, wheresimilar reference characters denote corresponding features consistentlythroughout the figures, there are shown preferred embodiments.

FIG. 1 illustrates ISC architecture for establishing the ISC session,according to embodiments as disclosed herein. The figure depicts the ISCenvironment with plurality of components of the ISC architecture.

As per the standard specification provided by the OMA alliance, the ISCarchitecture includes an ISC enabler 111 including plurality offunctional components and supported by external functional components112. In the communication device, the ISC enabler 111 includes an ISCclient 101 (initiator ISC client), an ISC client 102 (recipient ISCclient) and an ISC client 103 (recipient ISC client) associated with acommunication device 100 a, 100 b and 100 c respectively. In the networkdomain, the ISC enabler 111 includes an ISC server 105, an ISC XMLDocument Management Server (ISC XDMS) 106 and an ISCCP Gateway (CPGateway) 107. The ISC enabler functional components in a network domainare supported by external functional components 112 including but notlimited to SIP/IP core of the core network 104, a content provider 108,a remote ISC environment 109 and a supporting server 110.

The method disclosed allows the initiator ISC client 101 to initiate theISC session for content viewing and/or communication among ISC users ofcommunication devices 100 b and 100 c respectively in the ISCenvironment depicted by the FIG. 1. The ISC session initiation requestis communicated to the ISC server 105 of the ISC enabler through theSIP/IP core of the core network 104 that provides SIP/IP-basedfunctionalities required by the ISC enabler.

As a person skilled in the art understands that the initiator ISC client101 can have access to contents list for specifying the content to beviewed during the content viewing.

In an embodiment the initiator ISC client 101 can retrieve the contentslist after performing the procedures specified in filed PS application4142/CHE/2013 for retrieving the contents list. The content list formatcan be as specified in the PS application 4142/CHE/2013.

However, the media function in the ISC server 105 generates a requesttowards ISC CPGateway 107 if the requested content packets are alreadynot available with the media function. Further, the ISC CPGateway 107can request the content provider 108 to provide the required contentpackets to be delivered to the ISC clients participating in the session.

In an embodiment, the content received by the media function of the ISCserver 105 from the ISC CPGateway 107 is unicast or multicast packets.

The ISC session is initiated by the initiator ISC client 101 onreception of ISC session establishment request from the ISC user of thecommunication device 100 a. Based on the type of request from the ISCuser, the ISC session initiated by the initiator ISC client 101 can bethe personal ISC session only for the content viewing. The initiated ISCsession can also be the one to one ISC session between ISC users ofcommunication devices 100 a and 100 b respectively for the contentviewing and/or the communication. The initiated ISC session can also bethe group ISC session between ISC users of communication devices 100 a,100 b and 100 c respectively for the content viewing and/or thecommunication. The method allows the initiator ISC client 101 to sendthe first SIP INVITE for the content viewing to the ISC server 105 byappending one or more first parameters. The method allows the initiatorISC client 101 to send the second SIP INVITE for the communication byappending one or more second parameters.

The exchange of control signals and messages between the initiator ISCclient 101 and one or more recipient ISC clients 102 and 103respectively is managed by the media function and the communicationfunction of the ISC server to establish ISC session as received in thefirst SIP INVITE and second SIP invite. However, control signals andmessages are exchanged among other functional components within the ISCserver 105 and external functional components 112 of the ISC enablersuch as the supporting server 110 and the remote ISC environment 109which resides in other network environment.

The ISCConvergenceID appended to both the first SIP INVITE and thesecond SIP INVITE enables the media function and the communicationfunction to identify interrelation between initiated content viewing andcommunication. Thus, the ISCConvergenceID integrates the content viewingand the communication if the ISC user requests the ISC session for boththe content viewing and the communication.

The session type appended to both the first SIP INVITE and the secondSIP INVITE indicates one or more recipient ISC clients whether thereceived first SIP INVITE and the second SIP INVITE are for only contentviewing, only communication or both the content viewing and thecommunication.

On establishment of the requested ISC session, the media functiondelivers the requested content to one or more participants in the ISCsession.

The content available to one or more participants of the ISC session(for example, ISC users of communication devices 100 a, 100 b and 100 crespectively) can be a unicast or multicast content.

In an embodiment, the content can be media content such as a livecontent, a video on demand and the like provided by the content provider108.

In an embodiment, the method allows the ISC clients 101, 102 and 103respectively and the media function of the ISC server 105 to use any ofthe unicast or multicast protocols such as User Datagram Protocol (UDP)or Real-time Transport Protocol (RTP) (UDP/RTP), Internet GroupManagement Protocol (IGMP) and the like for receiving and delivering thecontents to be viewed.

The established ISC session for communication can be a chat session, avideo call, a voice over IP (VoIP) call and the like based on the choiceof communication selected by the ISC user.

In an embodiment, the ISC user can change the content being viewedwithout tearing down the established ISC session using a SIP re-INVITEmessage.

In an embodiment, during an ongoing one to one ISC session, if a valueof synchronization field Sync in the SIP re-INVITE message is set (yes)indicates the media function that the recipient ISC client has to besynchronized for content viewing. Thus, changes on content being viewedare reflected while delivery of content to the recipient ISC client.

However, for the group ISC session, the synchronization field Sync canbe set (yes) as a default setting, thus synchronizing the content viewedby all the participants (group members) of the ISC group session.

In an embodiment, the method enables one or more ISC clients to provideone or more ISC users with RTSP controls with respect to the contentbeing viewed in the personal ISC session, the one to one ISC session orthe group ISC session.

The communication devices 100 a, 100 b and 100 c respectively areillustrated for simplicity of understanding. However, the ISCenvironment can include a plurality of communication devices capable ofparticipating in the ISC session on receiving a request from anyinitiator ISC client in the ISC environment.

FIG. 2 is the example illustration of UI on communication devicesparticipating in the ISC session, according to embodiments as disclosedherein. The FIG. 2 depicts UI 201 displayed to the ISC user of thecommunication device 100 a. The ISC user can select the desired mode ofISC session. The ISC session can be the personal ISC session, the one toone ISC session or the group ISC session for only content viewing, foronly communication or both. If the ISC user selects the personal ISCsession the content delivered to the ISC user for example can be asdepicted by UI 202. The method enables the media function of the ISCserver 105 to deliver the desired contents along with associated contentwith reference to the content being viewed. The associated contents canbe various types of media content such as text, static image, audio orvideo clips and the like used to provide enhancements or supplementaryinformation to a main content being viewed.

For example, the associated contents provided along with the contentdelivered can be indicated to the ISC user using icons. The ISC user canclick on the icons to retrieve additional information. For example, theISC user can browse through history of a place while content deliveredto the ISC user displays live match being played at the place.

The UI 203 of the communication devices 100 a and 100 b respectivelyengaged in the one to one ISC session for the content viewing and thecommunication are depicted. For example, the common content being viewedis displayed in a larger window on screens of both the communicationdevices 100 a and 100 b respectively, while a smaller window is openedto allow the chat communication session between the ISC usersparticipating in the session.

The UI 204 of the communication devices 100 a, 100 b and 100 cparticipating in the group ISC session for the content viewing andhaving a chat communication are depicted.

However, if the ISC user selects to communicate with one or more ISCusers participating in the one to one ISC session or the group ISCsession using the video call or the voice call, a corresponding videocall window or a voice call icon can be displayed on the communicationdevices of the participating ISC users.

The UI described is an example interface and not a limitation and can becommunication device implementation specific.

FIG. 3 illustrates modules of a communication device for establishingthe ISC session, according to embodiments as disclosed herein. Thecommunication device 100 a includes the ISC client 101, a communicationinterface module 301, a display module 302 and a memory module 303. TheISC client 101 is configured to function as the initiator ISC clientwhen the ISC user request for establishing the ISC session and isconfigured to function as the recipient ISC client when the ISC clientreceives the first Session Initiation Protocol (SIP) invite and/or thesecond SIP INVITE from the ISC server for participating in the initiatedISC session for the content viewing and/or the communication. The ISCclient 101 is configured to receive request from the ISC user forestablishing the ISC session for the content viewing and/orcommunication and initiate various SIP based messages and controlsignals towards the ISC server 105. The ISC client 101 is configured toappend one or more first parameters to the first SIP INVITE and/or oneor more second parameters to the second SIP INVITE sent to the ISCserver for establishing the ISC session. Further, the ISC client 101 isconfigured to send and receive other control signals and messages forestablishing and managing the ISC session including but not limited tosending and receiving various SIP signals to and from the communicationfunction and/or the media function of the ISC server 105. The displaymodule 301 can provide the necessary user interface for the ISC client101 to receive ISC session establishment request from the user as wellas provide indications to the ISC user depicting progress of theinitiated ISC session. The communication interface module 302 providesthe necessary communication interface to the ISC client 101 tocommunicate with the ISC server 105.

The ISC client 101 when configured to function as recipient ISC clientnotifies the ISC user about incoming request to join initiated ISCsession and sends control signals and messages to the ISC server 105based on whether the ISC user desires to join or leave the ISC session.

The memory module 303 stores contact details and group details of otherISC users, to be used by the ISC client 101 during the initiation of theISC session.

For simplicity and ease of understanding, the modules in communicationdevice 100 a are limited to the embodiments of the invention. However,the communication device 100 a includes various other modules to supportadditional functionalities and operations of the communication device100 a.

Although it is illustrated in FIG. 3 that the modules are present in thecommunication device 100 a, it has to be understood by a person ofordinary skill in the art to incorporate the same modules in othercommunication devices such as communication device 100 b andcommunication device 100 c. The names of the modules of thecommunication device 100 a are used for illustrative purposes only andshould not be considered as a limitation.

FIG. 4 illustrates modules of the ISC server for establishing the ISCsession initiated by the communication device, according to embodimentsas disclosed herein. The ISC server 105 includes a media function 401and a communication function 402 along with other functional componentsas defined by the OMA. However for simplicity of understanding thefunctional components relevant to the method disclosed are illustratedand explained. The other functional components of the ISC serverincluding but not limited to a contents guide function, an associatedcontents guide function, a multi-device discovery function, a socialfunction, a storage function perform functions to support the mediafunction 401 and the communication function (CPM) 402 as defined in theOMA standard. Also, the functional interaction between the functionalcomponents is as defined in the OMA standard and is not explained forsimplicity. The media function 401 and the communication function 402 isconfigured to receive SIP based control signals and messages from one ormore the ISC clients in the ISC environment related with the contentviewing and the communication for the initiated ISC session. The mediafunction 401 is configured to receive and forward the first SIP INVITEsignal received from the initiator ISC client 101 to the recipient ISCclient 102. Whenever the group ISC session is initiated for thepre-defined group, the media function 401 is further configured toobtain the group members of the pre-defined ISC group and pre-definedpolicy of the pre-defined ISC group participating in the group ISCsession from the ISC XDMS 106. The media function 401 is configured toidentify the pre-defined group based on an ISC GroupID (GroupID)received in the first SIP invite.

On receiving a first SIP INVITE accept message from one or morerecipient ISC clients, the media function 401 is configured to deliverthe content to the one or more recipient ISC clients for the contentviewing.

The communication function 402 which is the communication function ofthe ISC Server side functional component directly refers to the CPMEnabler server side functional components to support interaction amongthe ISC users and between the ISC User and the content provider. Thecommunication function 402 is configured to receive and forward thesecond SIP INVITE signal received from the initiator ISC client 101 tothe recipient ISC client 102.

The names of the modules of the ISC server 105 are used for illustrativepurposes only and should not be considered as a limitation.

In an embodiment, the ISC server 105 can be configured to integrate thefunctionalities of the media function 401 and the communication function402 in a single functional component.

FIG. 5 is the flow diagram illustrating a method 500 for establishing anISC session for content viewing and/or communication, according toembodiments as disclosed herein. At step 501, the method 500 includesreceiving request from the user (ISC user) for initiating the ISCsession for content viewing and/or communication. In an embodiment, themethod 500 allows the initiator ISC client 101 to receive request fromthe ISC user of the communication device 100 a for initiating the ISCsession for the content viewing and/or the communication. At step 502,the method 500 includes determining whether the initiated ISC session isfor the content viewing and the communication.

In an embodiment, the method 500 allows the initiator ISC client 101 todetermine whether the initiated ISC session is for the content viewingand the communication. If it is determined at step 502, that theinitiated ISC session is for the content viewing and the communication,then at step 503, the method 500 includes sending the first SIP INVITEfor content viewing appended with one or more first parameters. In anembodiment, the method 500 allows the initiator ISC client 101 to sendthe first SIP INVITE for content viewing appended with one or more firstparameters.

The initiated ISC session can be the personal ISC session, the one toone ISC session or the group ISC session. Further, once the ISC sessionis established by and the ISC server based on the request received fromthe initiator ISC client any participant can be added or removed fromeither or both the content viewing and the communication in theestablished ISC session by the ISC server.

In an embodiment, the ISC server allows one or more recipient ISCclients participating in the established ISC session to voluntarilyleave the ISC session.

In an embodiment, one or more first parameter includes but is notlimited to an ISC feature tag (feature tag), a content ID (ContentRef),the ISCConvergenceID, the ISC SessionType, the ISC GroupID, a UniformResource Identifier (URI) list, a synchronization field Sync and a mRealTime Streaming Protocol (mRTSP).

The ISC feature tag in the first SIP INVITE indicates the ISC server 105whether the initiated ISC session is for establishing the personal ISCsession, the one to one ISC session or the group ISC session for contentviewing. The ISC Client includes both an IMS Communication ServiceIdentifier (ICSI) and an IMS Application Reference Identifier (IARI)feature tag in the Accept-Contact header, Contact header andP-Preferred-Service header as per [RFC3841], [RFC3840], if the ISCServer has to behave differently when it receives IARI, else the ISCClient includes only ICSI feature tag in the request.

For example CV_FT (Content Viewing Feature Tag) is an ISC feature tagset to: −+g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.omalsc.<isc-feature>” when it iscarried as a feature tag in a Contact or Accept-Contact header; and,−urn:urn-7:3gpp-service.ims.icsi.oma.isc.<isc-feature> when it iscarried as a URN in a P-Preferred-Service or P-Asserted-Service headeras described in [3GPP TS 24.229].

The table 1 provided below describes the ISC feature tag.

TABLE 1 ISC Session requested by <isc-feature> ISC user (ISC featuretag) Description ISC Content cv-cm = +g.3gpp.icsi- ICSI identifier forcontent viewing and Viewing and ref = “um%3Aurn-7%3A3gpp- communicationintegration session. Communication service.ims.icsi.oma.isc.cv-Integrated cm Session Personal self-cv = +g.3gpp.icsi- This IARIidentifier is used when ISC user content ref = “um%3Aurn-7%3A3gpp- isinitiating ISC session for content Viewingservice.ims.iari.oma.isc.self- viewing. cv One to one 1-1-cv-cm =+g.3gpp.icsi- This IARI identifier is used when ISC user content ref =“um%3Aurn-7%3A3gpp- is initiating ISC session with another ISC viewingservice.ims.iari.oma.isc.1-1- user for content viewing and cv-cmcommunication or content viewing only. Group group-cv-cm = +g.3gpp.icsi-This IARI identifier is used when user is Content ref =“um%3Aum-7%3A3gpp- initiating content viewing and Viewingservice.ims.iari.oma.isc.group- communication sessions in the ISC group.cv-cm

The ISC components reuse the Supporting Enabler ICSI (e.g., forCPM=+g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.session) in CPM_FT, if the ISCClient request is processed by the Supporting Enabler Server components.

The ContentRef or the content ID corresponds to reference to the userselected content identified from the content list in the media function401 for the content viewing. The content ID or the ContentRef identifiesthe content and is unique per content. It can be SIP Uniform ResourceIdentifier (URI) and/or channel number. This identifier is used in theRequest-URI header of the SIP request.

The ISCConvergenceID is an ISC specific header field. Including theISCConvergenceID in the SIP MESSAGE request or SIP INVITE request whichis globally unique identifier that indicates the ISC request andresponse associated with an ISC content viewing and communication,content interest. All requests and responses belonging to the same ISCcontent viewing and communication or the same content interest carry thesame value for the ISCConvergenceID header field. Sending ISC functionalcomponent includes an ISCConvergenceID header field in each SIP MESSAGErequest or SIP INVITE request that are associated with the ISC contentviewing and communication, content interest. The sending ISC functionalcomponent ensures that the included ISCConvergenceID is globally unique.

The synchronization field Sync in the SIP INVITE/re-INVITE request canbe set (yes) or reset (no). The field and corresponding value areincluded in a Multipurpose Internet Mail Extensions (MIME) body of theSIP INVITE request which indicate whether the participants in the ISCsession are to be synchronized for content viewing. Value “yes”indicates that both ISC Users in 1-1 session belonging to the sameISCConvergenceID should be synchronized in Content Viewing. Value “no”indicates that both ISC Users in 1-1 session belonging to the sameISCConvergenceID do not want to synchronize their Content Viewing. SoISC Server Media Function checks the value included in the “Sync”element is “yes” in the MIME SDP body of the SIP INVITE request and thengenerate a SIP INVITE request according to the rules and procedures of[RFC3261] and forwards it towards the recipient ISC client. Otherwise,the ISC Server Media Function does not forward the SIP INVITE requesttowards the recipient ISC Client.

The ISC SessionType indicates whether the initiated ISC session is forcontent viewing and/or communication. For example, the ISC SessionTypefield in the first SIP INVITE or the second SIP INVITE request includesvalues such as CV (Content Viewing)/CM (Communication)/CV-CM (ContentViewing and Communication). The ISC SessionType can be used by anyrecipient ISC client to determine whether it has to wait for another SIPINVITE after receiving a SIP INVITE which can be the first SIP INVITE orthe second SIP INVITE. If ISC SessionType is CV-CM, then the recipientISC client waits for two SIP INVITES (for content viewing andcommunication) before responding to the received SIP invite. Once therecipient ISC client receives both the first SIP INVITE and the secondSIP INVITE, it may notify the ISC user corresponding to the recipientISC client about the received SIP invites is for both content viewingand communication session. If the ISC SessionType is CV, then therecipient ISC client can immediately notify and respond according to theISC user consent to the received first SIP INVITE with acceptance forcontent viewing session only. If the ISC SessionType is CM, then therecipient ISC client can notify immediately and respond according to theISC user consent for the received second SIP INVITE for acceptance forcommunication ISC session only.

The ISC GroupID corresponds to the pre-defined ISC group for the groupISC session, the URI list corresponds to the group members in the groupISC session and the mRTSP corresponds to a request to the media function401 to gain RTSP controls.

The method 500 allows the initiator ISC client 101 to determine whichparameters from one or more first parameters is to be appended to thefirst SIP INVITE based on type of the ISC session request received fromthe ISC user. Thus, whether all or combination of one or more firstparameters are appended to the first SIP INVITE is based on the type ofISC session requested by the ISC user and is described accordingly insequence diagrams from FIG. 6 onwards.

At step 504, the method includes sending the second SIP INVITE forcommunication appended with one or more second parameters. In anembodiment, the method 500 allows the initiator ISC client 101 to sendthe second SIP INVITE for communication appended with one or more secondparameters. For example, the appended one or more second parameterincludes but is not limited to the ISC SessionType, the URI list and acommunication session identifier assigned with the ISCConvergenceID. Thecommunication session identifier is a communication conversation ID(CPM_Conv_ID).

Whether all or combination of one or more second parameters are appendedto the second SIP INVITE is based on the type of ISC session requestedby the ISC user and is described accordingly in sequence diagrams fromFIG. 6 onwards.

At step 505, the method 500 includes establishing the ISC session forthe content viewing based on received one or more first parameters. Inan embodiment, the method 500 allows the media function 401 to establishthe ISC session for the content viewing based on the received one ormore first parameters. At step 506, the method 500 includes establishingthe ISC session for the communication based on received one or moresecond parameters. In an embodiment, the method 500 allows thecommunication function 402 to establish the ISC session for thecommunication based on received one or more second parameters.

If it is determined that at step 502 that the initiated ISC session isfor the only content viewing, then at step 507, the method 500 includessending the first SIP INVITE for content viewing appended with one ormore first parameters. In an embodiment, the method 500 allows theinitiator ISC client 101 to send the first SIP INVITE for contentviewing appended with one or more first parameters to the media function401. At step 508, the method includes establishing the ISC session forthe content viewing based on the received one or more first parameters.In an embodiment, the method 500 allows the media function 401 toestablish the ISC session for the content viewing based on the receivedone or more first parameters.

If it determined at step 502 that the initiated ISC session is for theonly communication, then at step 509, the method 500 includes sendingthe second SIP INVITE for communication appended with one or more secondparameters. In an embodiment, the method 500 allows the initiator ISCclient 101 to send the second SIP INVITE for communication appended withone or more second parameters. Further, the method 500 includesperforming step 506 to establish the ISC session for communication.

The various actions, acts, blocks, steps, and the like in method 500 maybe performed in the order presented, in a different order orsimultaneously. Further, in some embodiments, some actions, acts,blocks, steps, and the like may be omitted, added, modified, skipped,and the like without departing from the scope of the invention.

FIG. 6 is the example sequence diagram illustrating establishing of thepersonal ISC session for the content viewing when the contents areavailable to the ISC client of the communication device as unicastcontent and changing of the content being viewed is performed throughthe SIP re-INVITE, according to embodiments as disclosed herein. FIG. 6depicts the initiator ISC client 101, the ISC server 105 including themedia function 401 and the communication function 402 and theISCCPGateway 107 exchanging SIP messages for establishing contentviewing for the personal ISC session. The initiator ISC client 101already has access to the content list after the media function 401request and receives (601) the desired contents of the content list fromthe content provider through the ISCCPGateway 107.

Upon receiving the request from the User to watch content, identified bythe ContentRef, the initiator ISC client 101 generates the first SIPINVITE request as defined in IETF RFC 3261.

The first SIP INVITE includes:

1. The ISC feature tag CV_FT with a value as defined in Table 1 forinitiating content viewing for self. CV_FT with ICSI value(+g.3gpp.icsi-ref=“urn %3Aurn-7%3A3gpp-service.ims.icsi.omalsc.cv-cm) isincluded in Accept-Contact header field, Contact header field andP-Preferred-Service header field. And CV_FT with IARI value(+g.3gpp.icsi-ref=”urn %3Aurn-7%3A3gpp-service.ims.iari.oma.isc.self-cv)is included in Accept-Contact header field.

2. Include globally unique identifier (new value is generated if it isfor initiating new content viewing session otherwise from existingcontent viewing session) for determining the content viewing associatedto ISC Convergence in the ISCConvergenceID. For example this field canbe included in the SIPINVITE.

3. Include the SDP for Content Viewing as below:

3.1 Include the ContentRef corresponding to the content 1 the ISC userhas selected to watch. The value of this field is obtained from thecontents list. For example the value of ContentRef is included in theMIME SDP body of the SIP INVITE under new Content-Type header field“application/ISC-content-request+xml”. The initiator ISC client 101generates the first SIP INVITE as described above and sends (602) therequest to the media function 401 of the ISC Server 105 withISCConvergenceID=1 for ContentRef=1 which identifies the ISC userselected content (content 1) from the content list in the provided bythe media function 401.

The values of ContentRef such as ContentRef=1, ContentRef=2 are examplevalues representing content IDs of corresponding contents the user isinterested in for the content viewing.

On receiving the first SIP invite, the media function 401 identifiesthat ISC feature tag received is for personal ISC session (self contentviewing) which indicates the media function 401 that the received firstSIP INVITE is not to be forwarded any further to any of the ISC clientsin the ISC environment.

Further, the communication between the media function and the initiatorISC client continues with a SIP INVITE accept message such as a 200 OK(603) as defined in conventional SIP procedures known in the art.

In accordance with the conventional procedure used both the initiatorISC client 101 and the ISC server 105 are aware that the contentidentified by ContentRef from the content list is available as unicastcontent. Further, the media function 401 starts (604) delivering thecontent corresponding to ContentRef=1 in the UDP/RTP tunnel. The ISCuser now watches the content as per his/her request.

Later, if the ISC user desires to change the content being viewed, thenthe ISC user requests the initiator ISC client 101 to change thecontent. The initiator ISC client 101 generates the SIP re-INVITE withparameters similar to the first SIP invite, except the ContentRef isassigned value ‘2’ which is associated with the new selected contents.The initiator ISC client retains the value of the ISCConvergenceID=1 asassigned during the first SIP invite. Further, the initiator ISC client101 sends (605) the SIP re-INVITE to the media function 401.

Thus, this enables the media function 401 changing of the contents inthe same established ISC session without tearing down the existing ISCsession.

The media function responds (606) with the 200 OK in response to thereceived SIP re-INVITE. Further, both initiator ISC client 101 and ISCserver 105 are aware that the content identified by ContentRef=2 isavailable to the ISC user as unicast content according to the contentslist. Further, the media function 401 starts (607) delivering the newcontent corresponding to ContentRef in the same UDP/RTP tunnel. The ISCuser now watches the changed content (content 2) as per request.

The steps described in FIG. 6 can be adapted in embodiments based ondifferent protocols such as an Internet Group Management Protocol (IGMP)and a Real Time Streaming Protocol (RTSP) with suitable modifications asdescribed later in FIG. 7 and FIG. 8 respectively. However, thedescription common between of FIG. 6, FIG. 7 is not repeated in FIG. 7for brevity.

FIG. 7 is the example sequence diagram illustrating establishing of thepersonal ISC session for content viewing when contents are available tothe ISC client as multicast content and changing of the content beingviewed is performed through the SIP re-INVITE, according to embodimentsas disclosed herein. The FIG. 7 depicts the personal ISC session basedon the Internet Group Management Protocol (IGMP). As described in FIG. 6suitable modifications in accordance with the corresponding technologycan be adapted to establish and handle the personal ISC session based onthe IGMP.

As described at 603 of FIG. 6 the media function 401 responds with the200 OK in response to the first SIP INVITE. Further, as the initiatorISC client 101 and the ISC server 105 are aware that the contentidentified by ContentRef=1 is available to the ISC user as multicastcontent from the contents list the initiator ISC client 101 sends (701)IGMP join request towards the media function 401 for joining themulticast group address for receiving the content.

Further, after receiving the 200 OK response as described in 606 of FIG.6 from the media function 401, the initiator ISC client 101 sends (702)IGMP leave request towards the media function 401 for departing fromcurrent watching content by specifying the multicast address and portnumber of the content. Further, the initiator ISC client 101 sends (703)the IGMP join request towards the media function 401 to change thecontent by specifying the multicast address and port number of the newcontent. Further, as depicted in 607 of FIG. 6 the media function 401starts multicasting the content for ContentRef=2 in the UDP/RTP tunnel.The ISC user now watches the new content changed (content 2) as perrequest.

In an embodiment, on receiving the request from the ISC user to changethe content being viewed, the method allows the initiator ISC client 101to send the content change indication in the IGMP leave request itselfand eliminates the need to send the SIP re-INVITE.

FIG. 8 is the example sequence diagram illustrating establishing of thepersonal ISC session for content viewing when contents are available tothe ISC client as unicast content and RTSP controls are provided to auser of the mobile communication device, according to embodiments asdisclosed herein. The figure depicts the initiator ISC client 101, theISC server 105 including the media function 401 and the communicationfunction 402 and the ISCCPGateway 107 exchanging SIP messages forestablishing content viewing for the personal ISC session. As theinitiator ISC client 101 already has access to the content list afterthe media function request and receives (801) the desired contents ofthe content list from the content provider through the ISCCPGateway 107.The initiator ISC client sends (802) the first SIP INVITE as describedin step 602. To indicate RTSP controls request to the media function,the initiator ISC client 101 includes the m-line for setting up the RTSPsession in the MIME body of the SIP INVITE under new Content-Type headerfield “application/ISC-content-request+xml” in the first SIP invite. Onreceiving the first SIP invite, the media function 401 identifies thatISC feature identifier received is for personal ISC session whichindicates that the received first SIP INVITE is not to be forwardedfurther to any of the ISC clients in the ISC environment. The mediafunction 401 responds with (803) the SIPINVITE accept message such asthe 200 OK signal. The ISC server 105 has capability to accept or rejectthe RTSP request for the selected content through the 200 OK signal.

As both the initiator ISC client 101 and the ISC server 105 are awarethat the content identified by ContentRef is available as unicastcontent. Thus, the initiator ISC client 101 sends (804) RTSP PLAYrequest with Uniform resource locator (URL) towards the ISC Server 105to establish a RTSP session for receiving the content identified in theContentRef with user controls. The media function 401 starts (805)delivering the content corresponding to ContentRef=1 in the UDP/RTPtunnel (RTSP session). The ISC user watches the content as per therequest. After receiving a request from the ISC user to pause thecontent that is being viewed, the initiator ISC client 101 sends (806)RTSP PAUSE request towards the media function 401. The ISC user is alsoallowed to perform other RTSP trick play commands such as FORWARD,REWIND, SKIP and the like. Upon receiving the request from the ISCClient 101 to pause the content, the media function 401 temporarily stop(807) delivering the media related to the content in the UDP/RTP tunnel(RTSP session). Upon request from the ISC user to resume the contentthat is being paused, the initiator ISC client 101 sends (808) RTSP PLAYrequest to the media function 401. Upon receiving the request from theISC Client 101 to resume the content, the media function 401 startsdelivering the temporarily halted content in the UDP/RTP tunnel (RTSPsession) from the position where it stopped by the ISC user.

FIG. 9 is the example sequence diagram illustrating initiation of theone to one ISC session for content viewing and communication, accordingto embodiments as disclosed herein. The FIG. 9 depicts the initiator ISCclient 101, the recipient ISC client 102, the ISC server 105 includingthe media function 401 and the communication function 402 and the ISCCPGateway 107 exchanging SIP messages for establishing the contentviewing and the communication for the one to one (1-1) ISC session.

Upon receiving the request from the ISC user A of the communicationdevice 100 a, associated initiator ISC client 101 performs one of thefollowing actions:

1. To watch content identified by ContentRef=1 and communicate with ISCuser of communication device 100 b associated with recipient ISC client102, the initiator ISC client 101 generates two SIP INVITE (SIP invite)requests. The first SIP INVITE is towards inviting recipient ISC client102 for content viewing and the second SIP INVITE for inviting recipientISC client 102 for communication.

2. To watch content identified by ContentRef=1, but no communicationwith the ISC user B of the recipient ISC client 102, the initiator ISCclient 101 generates only the first SIP INVITE towards inviting therecipient ISC client 102 for content viewing and the second SIP INVITEfor communication is not generated.

3. To communicate with the recipient ISC client but not interested towatch content together, the initiator ISC client 101 generates onlysecond SIP INVITE towards inviting the recipient ISC client forcommunication and the first SIP INVITE for content viewing is notgenerated.

The sequence diagram in the figures depicts the one-to-one ISC sessionfor content viewing and communication. As the initiator ISC client 101already has access to the content list after the media function 401request and receives (901) the desired contents of the content list fromthe content provider through the ISC CPGateway 107. Upon receivingrequest by the initiator ISC client 101 for the content viewing and thecommunication, the initiator ISC client generates the first SIP INVITEfor the content viewing as defined in IETF RFC 3261 with the followingclarifications as disclosed by the method:

1. Include the ISC feature tag CV_FT with a value as defined in Table 1for initiating 1-1 content viewing and communication. CV_FT with ICSIvalue (+g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.omalsc.cv-cm) is included inAccept-Contact header field, Contact header field andP-Preferred-Service header field and CV_FT with IARI value(+g.3gpp.icsi-ref=”urn %3Aurn-7%3A3gpp-service.imslari.omalsc.1-1-cv-cm)is included in Accept-Contact header field.

2. Include globally unique identifier (new value is generated if it isfor initiating new content viewing session otherwise from existingcontent viewing session) for determining the content viewing associatedto ISC Convergence in the ISCConvergenceID. For example this field canbe included in the SIP INVITE.

3. Include the SDP for content viewing and the below headers in the body

3.1. Include the ContentRef corresponding to the content the ISC usercorresponding to the initiator ISC client 101 has selected to watch. Thevalue of this field is obtained from the contents list. For example thevalue of ContentRef is included in the MIME SDP body of the SIP INVITEunder new Content-Type header field“application/ISC-content-request+xml”.

3.2. Include the ISC SessionType as CV-CM as the ISC session is for thecontent viewing and the communication. However, include the ISCSessionType as CV if the ISC session is only for the content viewing andinclude ISC SessionType as CM if the ISC session is only for thecommunication.

3.3. Include the synchronization field Sync which can be set (yes) orreset (no). The initiator ISC client 101 includes Sync=yes(synchronization field Sync value is set) stating both ISC users in 1-1ISC session should be synchronized in content viewing otherwise, theinitiator ISC client 101 includes Sync=no (synchronization field Syncvalue is set as false) stating both ISC users in 1-1 ISC session shouldnot be synchronized in content viewing.

Upon generating the first SIP invite, the initiator ISC client 101 sends(902) the first SIP INVITE towards the media function 401. Uponreceiving the first SIP INVITE request containing the ISC featureidentifier value pertaining to 1-1 content viewing and communication,the media function 401 identifies that the first SIP INVITE is to beforwarded to the recipient ISC client 102. Further, the media functionforwards (903) the first SIP invite to invite the recipient ISC client102 for the 1-1 content viewing session.

For setting up the communication, the initiator ISC client generates thesecond SIP INVITE as defined in IETF RFC 3261 with the followingclarifications:

1. Include the ISC feature tag ISCI as CPM_FT=+g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.session for initiating 1-1communication session.

2. Include the ISC feature tag (IARI) CV_FT=+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.ims.iari.oma.isc.1-1-cv-cm in the Accept-Contactheader field and Contact header field for initiating 1-1 communicationsession.

3. For determining the communication associated to CPM Conversation copythe value of ISCConvergenceID in the CPM_Conv_ID header field which isused for 1-1 content viewing. This identifies the initiated thecommunication within same ISC session in which the content viewingsession was initiated allowing integration of the content viewing andthe communication.

4. Include the SDP for communication and below headers in the SIP INVITEbody:

4.1. Include the ISC SessionType as CV-CM as the session is for thecontent viewing and the communication. However, if the session is onlyfor content viewing, include session type as CV and if the session isonly for communication include session type as CM. For example, thisfield can be included in the SIP INVITE body with new content type.

4.2. Include the ContentRef corresponding to the content the ISC usercorresponding to the initiator ISC client 101 has selected to watchunder new Content-Type header field“application/ISC-content-request+xml”.

Further, the initiator ISC client 101 sends (904) the second SIP INVITErequest towards the communication function 402 in the ISC Server 105.Further, the communication function forwards the second SIP INVITErequest to the appropriate ISC client such as the recipient ISC client102 depicted in the figure to invite for the 1-1 communication ISCsession. As the SIP INVITE for communication (the second SIP INVITE)) isreceived on a communication client of the communication function 402,the communication client forwards (905) the second SIP INVITE to therecipient ISC client 101 if the “SessionType” is included in the secondSIP INVITE received from the initiator ISC client 101.

As the method allows the initiator ISC client 101 to append the sessiontype in both the first SIP INVITE and the second SIP invite, thisenables the recipient ISC client 102 to identify the type of ISC sessioninitiated. Thus, irrespective of whether the first SIP INVITE or thesecond SIP INVITE is received first by the recipient ISC client 102, theSessionType indicates the recipient ISC client 102 whether it has toimmediately notify its ISC user of the received invitation or wait forone more SIP invites. For example, the recipient ISC client 102 checksif the value of “SessionType” element value is “cv-cm” in MIME SDP bodywith Content-Type header ‘application/ISC-content-request+xml’. If yesthen the ISC Client waits until SIP INVITE request for Communicationwith the CPM_FT ‘urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session’ andfor the same “ISCConvergenceID” is received.

If the ISC user accepts the invitation for the content viewing in theinitiated ISC session, the recipient ISC client 102 responds (906) with200 OK which is further forwarded by the media function to the initiatorISC client 101 if there are no errors to the request. If any errors aredetected, the media function 401 responds with error as specified inIETF RFC 3261.

The steps described in FIG. 9 are the steps for initiating the ISCsession for the content viewing and the communication. However, based onthe way the content is available to the initiator ISC client 101 and therecipient ISC client 102, further steps for delivering the content inthe UDP/RTP tunnel may vary and are described in FIG. 10, FIG. 11 andFIG. 12 later.

FIG. 10 is an example sequence diagram illustrating establishing of theone to one ISC session for content viewing and communication whencontents are available to ISC clients of the mobile communicationdevices participating in the one to one ISC session as unicast contentand changing of the content being viewed is performed through the SIPre-INVITE, according to embodiments as disclosed herein. The FIG. 10depicts the initiator ISC client 101, the recipient ISC client 102, theISC server 105 including the media function 401 and the communicationfunction 402 and the ISC CPGateway 107 exchanging SIP messages forestablishing the content viewing and the communication for the one toone (1-1) ISC session.

As described in the FIG. 9, the recipient ISC client 102 responds withthe 200 OK signal in response to the received first SIP invite. Further,the media function 401 starts (1001) delivering the contentcorresponding to ContentRef=1 in the UDP/RTP tunnel as unicast content.Both the ISC user A and ISC user B of the initiator ISC client 101 andthe recipient ISC client 102 respectively simultaneously watch the samecontent (specified by ContentRef=1) as per request for the 1-1 contentviewing session.

Further, the recipient ISC client 102 responds with (1002) 200 OK inresponse to the received forwarded second SIP INVITE and thecommunication function 402 forwards the 200 OK to the initiator ISCclient 101 if there are no errors to the request. If any errors aredetected the communication function responds error as specified in IETFRFC 3261. Thereafter, the ISC users of the initiator ISC client 101 andthe recipient ISC client 102 communicate (1003) with each other througha Message Session Relay Protocol (MSRP). Thus, the 1-1 integratedcontent viewing and the communication ISC session has been establishedbetween the ISC users. The integration is performed using globallyunique ISCConvergenceID same for the initiated content viewing and theinitiated communication. The CPM Client interacts with the ISC Client torender the media from Content Viewing and Communication Sessionstogether when the value of “ISCConvergenceID” is same.

Upon request from the ISC user of the initiator ISC client 101 to changethe content that is being viewed to another content, the initiator ISCclient generates the SIP re-INVITE similar to the first SIP INVITE asexplained in first SIP INVITE generation above but with changed contentID (ContentRef=2) under new Content-Type header field“application/ISC-content-request+xml” with the clarification asdisclosed by the method which allows addition of synchronization fieldSync which can be set (yes) or reset (no).

FIG. 10 depicts the initiator ISC client 101 includes Sync=yes(synchronization field Sync value is set) stating both ISC users in 1-1ISC session should be synchronized in content viewing. For example thisfield can be included in the SIP INVITE request MIME body with newcontent type.

Further, the initiator ISC client 101 sends (1004) the SIP re-INVITErequest towards the media function 401 including the ISCConvergenceID ofthe existing ISC content viewing session, which then forwards (1005) theSIP re-INVITE request to the recipient ISC client 102. Thereafter therecipient ISC client 102 auto-accepts and responds with (1006) 200 OK inresponse including the ISCConvergenceID header field and value asreceived in the SIP INVITE request if there are no errors to therequest. If any errors are detected the media function 401 returns erroras specified in IETF RFC 3261. Further the media function forwards the200 OK to the initiator ISC client 101. Further, the media functionstarts (1007) delivering the new content corresponding to ContentRef=2in the UDP/RTP tunnel. Thus, the ISC users participating in the one toone ISC session start receiving the same media related to the contentspecified in the ContentRef and watch the changed content.

Upon request from the ISC user A of the initiator ISC client 101 tochange the content that is being viewed to another content with the newcontent to be delivered only to the himself/herself, the initiator ISCclient 101 generates the SIP re-INVITE for content viewing by retainingthe ISCConvergenceID to maintain the same established ISC session.However, the SIP re-INVITE includes changed value of content ID(ContentRef=3) as per new request form the ISC user, but resets thevalue of the synchronization field Sync to false (Sync=no) as both theISC user A and B participating in the one to one ISC session are not tobe synchronized in content viewing. Further, the initiator ISC client101 sends (1008) the SIP re-INVITE towards the media function 401.

The media function checks if ISC user of the initiator ISC client isauthorized to watch different content in the 1-1 Content Viewing andCommunication ISC session. The media function 401 responds with (1009)the 200 OK in response to the SIP re-INVITE received if there are noerrors to the request. If any errors are detected the media function 401responds with error as specified in IETF RFC 3261.

Further, the media function 401 starts (1010) delivering the contentcorresponding to ContentRef=3 in the UDP/RTP tunnel only to theinitiator ISC client 101. Thus ISC user A watches different contentsthan that watched by ISC user B as per request of ISC user A.

In an embodiment the ISC user B may be notified that the ISC user A iswatching different content subsequent to subscription of ISC EventPackage.

Thus, the one to one ISC session for the content viewing and thecommunication session are continued with ISC user A watching differentcontent and communicating with ISC user B integrated throughISCConvergenceID.

The steps described in FIG. 10 can be adapted in embodiments based ondifferent protocols such as the IGMP and the RTSP with suitablemodifications as described later in FIG. 11 and FIG. 12 respectively.However, the description common between of FIG. 10, FIG. 11 is notrepeated in FIG. 11 for brevity.

FIG. 11 is the example sequence diagram illustrating establishing of theone to one ISC session for content viewing and communication whencontents are available to the ISC clients as multicast and changing ofthe content being viewed is performed through the SIP re-INVITE,according to embodiments as disclosed herein.

The FIG. 11 depicts the one to one ISC session based on the InternetGroup Management Protocol (IGMP). As described in FIG. 10 suitablemodifications in accordance with the corresponding technology can beadapted to establish and handle the one to one ISC session based on theIGMP as depicted in the FIG. 11 including but not limited to IGMP-GMRJoin 1 (1101), IGMP GMR leave 1 and IGMP GMR Join2 (1102), IGMP GMRleave2 (1103) and IGMP GMR Join 3 (1104).

Thus, the one to one ISC session for the content viewing and thecommunication session continues with ISC user A watching differentcontent and communicating with ISC user B integrated throughISCConvergenceID.

FIG. 12 is the example sequence diagram illustrating establishing of theone to one ISC session for content viewing and communication whencontents are available to the ISC clients as unicast content and RTSPcontrols are provided to the user, according to embodiments as disclosedherein. The FIG. 12 depicts the initiator ISC client 101, the recipientISC client 102, the ISC server 105 including the media function 401 andthe communication function 402 and the ISC CPGateway 107 exchanging SIPmessages for establishing the content viewing and the communication forthe one to one (1-1) ISC session with RTSP controls.

As described in the FIG. 9, the recipient ISC client 102 responds withthe 200 OK signal in response to the received first SIP INVITE (The ISCclient 101 sends (902) first SIP INVITE request by including the m-linefor setting up the RTSP session in the MIME body of the SIP INVITE undernew Content-Type header field “application/ISC-content-request+xml” inaddition (the SDP body contains media descriptions matching therequested media streams in the m-line for setting up the RTSP sessionaccording to the rules and procedures of [RFC2326] and [RFC4567]) to themedia function 401). As both the initiator ISC client 101 and therecipient ISC client 102 and the media function 401 are aware thatcontent identified by ContenRef is available as unicast content. Thus,the initiator ISC client 101 sends (1201) the RTSP play. Further, themedia function 401 starts (1202) simultaneously delivering the contentcorresponding to ContentRef=1 in the UDP/RTP tunnel (RTSP session) asunicast content to both the ISC user A and the ISC user B of theinitiator ISC client 101 and the recipient ISC client 102 respectivelyas per request received from the ISC user A for the 1-1 content viewingsession.

Further, the recipient ISC client 102 responds with (1203) 200 OK inresponse to the received forwarded second SIP INVITE and thecommunication function 402 forwards the 200 OK to the initiator ISCclient 101 if there are no errors to the request. If any errors aredetected the communication function responds with error as specified inIETF RFC 3261. Thereafter, the ISC users of the initiator ISC client 101and the recipient ISC client 102 communicate (1204) with each otherthrough the MSRP. Thus, the 1-1 integrated content viewing and thecommunication ISC session has been established between the ISC user Aand B. The integration is performed using globally uniqueISCConvergenceID same for the initiated content viewing and theinitiated communication.

Upon receiving the request from the ISC user A to pause the content thatis being viewed, the initiator ISC client sends (1205) RTSP PAUSErequest towards the media function 401. The ISC user is also allowed toperform other RTSP trick play commands such as FORWARD, REWIND, SKIP andthe like. Upon receiving the request from the ISC Client 101 to pausethe content, the media function temporarily stop (1206) delivering themedia related to the content in the UDP/RTP tunnel (RTSP session) toboth the initiator ISC client 101 and the recipient ISC client 102.

Unlike the existing method, the method allows RTSP controls to becontrolled by only one participant in the ISC session such as theinitiator ISC client 101.

In an embodiment, the RTSP control rights can be given to the recipientISC client.

Upon request from the ISC user A to resume the content that is beingpaused, the initiator ISC client sends (1207) RTSP PLAY request towardsthe media function 401. Upon receiving the request from the ISC Client101 to resume the content, the media function 401 starts (1208)delivering the temporarily halted content to both the initiator ISCclient 101 and the recipient ISC client 102 in the RTSP session from theposition, where it was stopped by the ISC user A.

FIG. 13 is the example sequence diagram illustrating establishing of theone to one ISC session for content viewing and communication when amedia function and a communication function are integrated in the ISCserver, according to embodiments as disclosed herein. The FIG. 13depicts the initiator ISC client 101, the recipient ISC client 102, theISC server 105 with the media function 401 and the communicationfunction 402 integrated and the ISC CPGateway 107 exchanging SIPmessages for establishing content viewing for the one to one ISCsession. As the initiator ISC client 101 already has access to thecontent list after the media function request and receives (1301) thedesired contents of the content list from the content provider throughthe ISC CPGateway 107.

As depicted in the FIG. 13 upon receiving the request from the ISC userA to watch content identified by ContentRef, and communicate with ISCuser B, the initiator ISC client generate a combined SIP INVITE requestwith two m-lines. The two m-lines include the SDP for content viewingfor inviting the ISC user B towards content viewing and the SDP forcommunication for inviting the ISC user B for communication.

However, if request received is for watching content identified byContentRef, but no communication with ISC User B, then initiator ISCclient 101 generates the combined SIP INVITE but does not include m-linefor communication.

If the request received is for communicating but not for watchingcontents, then initiator ISC client 101 generates the combined SIPINVITE but does not include mine for content viewing.

In response to the request for content viewing and communication theinitiator ISC client performs following actions:

1. Include the feature tag CV_FT which is for initiating 1-1 contentviewing and communication ISC session. For example the value of thisfeature tag could be +g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.omaisc.1-1-cv-cm”

2. Include the ContentRef corresponding to the content the ISC user Ahas selected to watch. The value of this field is obtained from thecontents list.

3. Include globally unique identifier for determining the ContentViewing associated to ISC Convergence in the ISCConvergenceID.

4. Include both m-line as the ISC session initiated is for both contentviewing and communication.

Further the initiator ISC client 101 sends (1302) the single combinedSIP INVITE request towards the ISC Server 105.

The ISC Server responds with a 200 OK in response to the SIP INVITEreceived if there are no errors to the request. If any errors aredetected the ISC Server media function responds with error as specifiedin IETF RFC 3261.

Upon receiving the request from the ISC user A, the ISC Server MediaFunction 401 forwards (1303) the combined SIP INVITE request torecipient ISC client 102 being invited to the 1-1 content viewingsession.

Further, the recipient ISC client 102 responds with 200 OK with SDP1:OK,SDP2:OK (combined SIP INVITE accept message) in response to theforwarded combined SIP INVITE received if there are no errors to therequest, stating the ISC user B accepts both the content viewing and thecommunication with ISC user A. If any errors are detected the ISC ServerMedia function 401 return error as specified in IETF RFC 3261. The ISCServer Media Function forwards the 200 OK to the initiator ISC Client102.

Further, the ISC Server Media Function 401 starts 1306) delivering thecontent corresponding to ContentRef in the UDP/RTP tunnel. ISC users Aand B have started watching the content as per request in the 1-1Content Viewing session. Further, ISC users A and B start communicatewith each other and 1-1 the content viewing and communication session isestablished between ISC users A and B. Now ISC users A and B arewatching the same content and communicating each other integratedthrough ISCConvergenceID.

FIG. 14 is the example sequence diagram illustrating establishing of thegroup ISC session among the pre-defined group for content viewing andcommunication when contents are available to the ISC clients of thepre-defined group as unicast content, according to embodiments asdisclosed herein.

The FIG. 14 depicts the initiator ISC client 101, the recipient ISCclient 102, the recipient ISC client 103, the ISC server 105 includingthe media function 401 and the communication function 402 and the ISCCPGateway 107 exchanging SIP messages for establishing the contentviewing and the communication for the group ISC session. As theinitiator ISC client 101 already has access to the content list afterthe media function request and receives (1401) the desired contents ofthe content list from the content provider through the ISC CPGateway107.

As discussed for the personal ISC session establishment and one to oneISC session establishment, the method allows the initiator ISC client101 to generate the first SIP INVITE and/or the second SIP INVITE basedon the request from the ISC user A for establishing the group ISCsession for the content viewing and/or the communication.

For the group ISC session the first SIP INVITE for the content viewingis generated as defined in IETF RFC 3261 with the followingclarifications provided by the method disclosed:

1. Include the ISC GroupID that corresponds to group address of thepre-defined ISC group. For example in the Request-URI

2. Include the ISC feature tag CV_FT which is for initiating groupcontent viewing and communication for the pre-defined ISC group. CV_FTwith ICSI value (+g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.omalsc.cv-cm) is included inAccept-Contact header field, Contact header field andP-Preferred-Service header field. And CV_FT with IARI value(+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.ims.iari.oma.isc.group-cv-cm) is included inAccept-Contact header field.

3. Include globally unique identifier (new value is generated if it isfor initiating new content viewing session otherwise from existingcontent viewing session) for determining the content viewing associatedto ISC convergence in the ISCConvergenceID.

4. Include the SDP for unicast content viewing and below headers in theSIP INVITE body

4.1. Include the ContentRef corresponding to the content the ISC user Ahas selected to watch. The value of this field is obtained from thecontents list. For example the value of ContentRef is included in theMIME SDP body of the SIP INVITE under new Content-Type header field“application/ISC-content-request+xml”.

4.2. As described for the personal ISC session or the one to one ISCsession include ISC SessionType as CV-CM as the session is for contentviewing and communication. However, include SessionType as CV if thesession is only for content viewing and as CM if the session is only forcommunication.

Further, the initiator ISC client 101 sends (1402) the first SIP INVITErequest towards the media function 401.

Upon receiving the first SIP INVITE request from the initiator ISCclient 101 containing the feature tag value pertaining to group contentviewing and communication for the group ISC session, the media function401 retrieves the group members of the pre-defined group and the policycorresponding to the ISC GroupID received in first SIP INVITE request,from the ISC XDMS 106. For example the policy allows the media functionto priory know which of the group members carries the group controls.

Further, the media function 401 forwards (1403) the first SIP INVITErequest towards each group member including recipient ISC client 102 and103 respectively, belonging to the predefined group identified from theISC GroupID specified in the received first SIP invite.

Further, for setting up the communication, the initiator ISC client 101fetches the group members from the ISC XDMS 106 if the communicationfunction does not have access to the group information defined in ISCXDMS 106. The initiator ISC client 101 generates the second SIP INVITErequest as defined in IETF RFC 3261 with the following clarifications asprovided by the method disclosed:

1. Include ISC GroupID if the communication function has access to thepre-defined group in ISC XDMS 106, else include URI list as obtainedabove.

2. Include the feature tag ICSI as CPM_FT=+g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.session which is for initiatinggroup communication session.

3. For determining the communication associated to CPM Conversation copythe value of ISCConvergenceID in the CPM_Conv_ID header field which isused for content viewing. This identifies the initiated thecommunication within same ISC session in which the content viewingsession was initiated allowing integration of the content viewing andthe communication.

4. Include the SDP for the communication and below headers in the SIPINVITE body

4.1. Include ISC SessionType as CV-CM as the session is for the contentviewing and communication, as CV if the session is only for contentviewing and as CM if the session is only for communication. However,include session type as CV if the session is only for content viewingand as CM if the session is only for communication. For example thisfield can be included in the SIP INVITE body with new content type.

Further, the initiator ISC client 101 sends (1404) the second SIP INVITErequest towards the communication function 402.

The communication function forwards (1405) the second SIP INVITE towardsrequest to each group member as the ISC SessionType is included in thereceived second SIP INVITE request.

As the method allows the initiator ISC client 101 to append the sessiontype in both the first SIP INVITE and the second SIP invite, thisenables the recipient ISC client 102 to identify the type of ISC sessioninitiated. The recipient ISC client 102 checks if the value of“SessionType” element value is “cv-cm” in MIME SDP body withContent-Type header ‘application/ISC-content-request+xml’. If yes thenthe ISC Client waits until SIP INVITE request for Communication with theCPM_FT ‘urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session’ and for thesame “ISCConvergenceID” is received. As the content viewing and thecommunication SIP messages are received by the recipient ISC clients 102and 103 respectively, the recipient ISC clients return 200 OK (1406 and1409 respectively) in response to the first SIP INVITE and the secondSIP INVITE respectively. Whenever there are any errors to the requestthe media function 401 and the communication function return error asspecified in IETF RFC 3261.

The media function 401 and the communication function 402 forward (1407and 1410 respectively) the 200 OK to the initiator ISC client 101.

Further, after sending the 200 OK the media function starts (1408)delivering the content corresponding to ContentRef in the UDP/RTP tunnelto all the group members. Simultaneously, the communication function 402allows the group members to communication through the MSRP (1411). Thus,the content viewing along with the communication for the group ISCsession is established and integrated through ISCConvergenceID.

The steps described in FIG. 14 can be adapted in embodiments based ondifferent protocols such as the IGMP and the RTSP with suitablemodifications in accordance with the corresponding technology.

As a person skilled in the art understands, removal of a participantfrom the ISC session, addition of a new participant to the ISC sessionfrom content viewing and/or communication or accepting leave requestfrom an existing participant from the ISC session is within the scope ofthe method disclosed. This can be performed using conventionalprocedures known in the art combined with the embodiments of the methoddisclosed using the parameters including but not limited to ISC GroupIDand ISCConvergenceID.

In an embodiment, for addition of a new ISC user the initiator ISCclient generates SIP REFER request as specified in RFC 3515 with thefollowing clarifications provided by the method disclosed by:

1. Include group identity (ISC GroupID) of the ongoing ISC group session(group ISC session).

2. Include the feature tag based on whether the initiation of SIP REFERis for the content viewing and/or the communication.

3. Include address of the recipient ISC client in Refer-to header calleda client ID. If more than one ISC user is invited, the Refer-To headerincludes a pointer to URI-List in the body and includes the URI-List inthe body.

4. Include method parameter of the Refer-to header as INVITE

5. Include the ContentRef corresponding to the content user has selectedto watch. In an embodiment additional content information correspondingto the current content being watched by the existing group members isincluded to provide additional information to the invitee.

6. Include globally unique identifier (from existing content viewingsession) for determining the content viewing associated to ISCConvergence in the ISCConvergenceID.

7. Include the SDP for unicast content viewing and below headers in thebody.

8. Include the ISC SessionType.

In an embodiment, the existing ISC user of the on-going group ISCsession can be terminated using SIP REFER and SIP BYE messages of theconventional procedure with suitable modification similar to theprocedure described for adding the ISC user.

In an embodiment, the ISC user desiring to leave the content viewingand/or communication indicates the desire and the ISC client associatedwith the ISC user generates and sends the SIP BYE. The SIP BYE includesongoing ISC GroupID, the feature tag ICSI, the SessionType based onwhether the termination is for content viewing and/or communication.Further, based on the session type the SIP BYE messages can be senttowards the media function and/or the communication functionrespectively.

FIG. 15 is the example sequence diagram illustrating changing thecontent being viewed by the pre-defined group through the SIP re-INVITEwhen contents are available to the ISC clients of the as unicast contentduring the group ISC session, according to embodiments as disclosedherein. The FIG. 15 depicts the initiator ISC client 101, the recipientISC client 102, the recipient ISC client 103, the ISC server 105 withthe media function 401 and the communication function 402 exchanging SIPmessages for content viewing and the communication for the group ISCsession. The FIG. 15 depicts group members of the pre-defined group arewatching the same content and communicating each other integratedthrough ISCConvergenceID.

Upon request from the group member (here the initiator ISC client 101)to change the content that is being viewed to another content, theinitiator ISC 101 generates the SIP re-INVITE for the SIP re-INVITE forthe personal ISC session or the one to one ISC session including the newContentRef with value of ContentRef=2 corresponding to the content beingselected by the ISC user A associated with the initiator ISC client 101.

Further, the initiator ISC client sends (1501) the SIP re-INVITE requesttowards the media function 401.

The media function 401 checks the group policy in the ISC XDMS 106 toconfirm whether the requesting ISC user is authorized to change thecontent. If the ISC user is not authorized, the request of therequesting group member is returned with error.

Further, the media function 401 (1502) forwards the SIP re-INVITErequest to the remaining group members (recipient ISC clients 102 and103 respectively) in the current established ISC session.

In an embodiment, the method does not include the synchronization fieldSync in the SIP re-INVITE; instead synchronization of the contentviewing among group members can be a default setting of the group ISCsession.

In an embodiment, the participants of the group ISC session (groupmembers) such as the recipient ISC clients 102 and 103 respectively autoaccept the received SIP re-INVITE request.

In an embodiment, the ISC clients 102 and 103 can notify change ofcontent to their respective ISC users and reply in accordance with theirISC users' response.

Further, the recipient ISC client 102 and 103 respectively return (1503)200 OK in response to the SIP re-INVITE. The media function forwards(1504) the 200 OK to the initiator ISC client 101. Thereafter, the mediafunction 401 starts (1505) delivering the content corresponding to newContentRef in the UDP/RTP2 tunnel. The group members now watch thechanged content as per request of the authorized group member.

FIG. 16 is an example sequence diagram illustrating establishing of thegroup ISC session among the pre-defined group for content viewing andcommunication when contents are available to the ISC clients in thepre-defined group as multicast, according to embodiments as disclosedherein.

The FIG. 16 depicts the group ISC session based on the IGMP. Asdescribed in FIG. 14 suitable modifications in accordance with thecorresponding technology can be adapted to establish and handle thegroup ISC session based on the IGMP as depicted in the FIG. 16.including but not limited to IGMP-GMR Join 1 (1601) and IGMP GMR Join 1(1602). Thus, group ISC session, integrated through ISCConvergenceID,for the content viewing and the communication is established based whenIGMP is utilized.

As a person skilled in the art understands, removal of a participantform the ISC session, addition of a new participant to the ISC sessionor terminating an existing participant from the ISC session is withinthe scope of the method disclosed and can be performed usingconventional procedures known in the art combined with the methoddisclosed.

FIG. 17 is the example sequence diagram illustrating changing thecontent being viewed by the pre-defined group through the SIP re-INVITEwhen contents are available to the ISC clients of the pre-defined groupas multicast content during the group ISC session, according toembodiments as disclosed herein. The FIG. 17 depicts the initiator ISCclient 101, the recipient ISC client 102, the recipient ISC client 103,the ISC server 105 including the media function 401 and thecommunication function 402 exchanging SIP messages for the contentviewing and the communication for the group ISC session. The FIG. 17depicts group members of the pre-defined group are watching the samecontent and communicating each other, integrated throughISCConvergenceID.

Upon request from the group member (here the initiator ISC client 101)to change the content that is being viewed to another content, initiatorISC client 101 generates the SIP re-INVITE including the new ContentRef(ContentRef=2) corresponding to the content being selected by the ISCuser A of the initiator ISC client 101.

Further, the initiator ISC client sends (1701) the SIP re-INVITE requesttowards the media function 401.

The media function checks the group policy in the ISC XDMS 106 toconfirm whether the requesting ISC user is authorized to change thecontent. If not authorized, requesting group member is returned witherror.

Further, the media function 401 (1702) forwards the SIP re-INVITErequest to the remaining group members (recipient ISC clients 102 and103 respectively) in the current established ISC session.

In an embodiment, in order for the other participating group members toreceive the same content, the recipient ISC clients 102 and 103respectively can auto accept the received SIP re-INVITE request.

Further, the recipient ISC client 102 and 103 respectively return (1703and 1707) 200 OK in response to the SIP re-INVITE. On reception of the200 OK signal from at least one of the recipient ISC client, the mediafunction forwards (1704) the 200 OK to the initiator ISC client 101.After signaling corresponding to the 200 OK is completed, theparticipating group members perform the IGMP leave (1705 and 1708) andIGMP join (1706 and 1709) to receive the changed contents (ContentRef=2)through multicast content. Further, the media function 401 delivers(1710) the contents requested by the ISC user A of the initiator ISCclient 101 with content corresponding to new ContentRef in the UDP/RTPtunnel. The group members now watch the changed content as per requestof the authorized group member.

FIG. 18 is the example sequence diagram illustrating establishing of thegroup ISC session for content viewing and communication when contentsare available to the ISC clients as unicast and RTSP controls areprovided to the user, according to embodiments as disclosed herein. TheFIG. 18 depicts the initiator ISC client 101, the recipient ISC client102, the recipient ISC client 103, the ISC server 105 including themedia function 401 and the communication function 402 and the ISCCPGateway 107 exchanging SIP messages for establishing the contentviewing and the communication for the group ISC session.

As described in FIG. 14, the method repeats the same steps to establishthe group ISC session for content viewing and the communication exceptthat the manner in which the content are available to the participatingISC clients is unicast with one of the group member allowed the RTSPcontrols (for example, during the RTSP session for video on demandservice). The media function 401 and the participating ISC clients arealready aware of the way content is available. Thus the steps describedbelow are performed in similar manner as described in FIG. 14 and arenot described in detail to avoid repetition.

The media function 401 receives (1801) the desired contents of thecontent list from the content provider through the ISC CPGateway 107,the initiator ISC client (101) sends (1802) first SIP INVITE requestwith mRTSP parameter included in the MIME SDP body (the SDP bodycontains media descriptions matching the requested media streams in them-line for setting up the RTSP session according to the rules andprocedures of [RFC2326] and [RFC4567]) to the media function 401. Themedia function 401 accesses the group members and the group policy forthe pre-defined group and forwards (1803) the first SIP INVITE to thegroup members (recipient ISC client 102 and 103 respectively). Further,the initiator ISC client 101 creates URI list and sends (1804) thesecond SIP INVITE based on the URI list to the communication function402. Further, the communication function 402 forwards (1805) the secondSIP INVITE to the group members (recipient ISC client 102 and 103respectively).

On reception (1806) and (1809) of 200 OK signal from the one or morerecipient ISC client by the media function 401, the media function sends(1807) 200 OK to the initiator ISC client 101. Thereafter, when theinitiator ISC client 101 sends RTSP play command, the media functionconfirms authorization whether the requesting member is allowed for RTSPcontrols and delivers (1810) the contents requested by the ISC user A ofthe initiator ISC client 101 in the UDP/RTP tunnel.

On reception (1811 and 1814) 200 OK from at least one of the recipientISC clients 102 and 103 respectively, the communication function 402sends (1812) 200 OK to the initiator ISC client 101. Further, thecommunication function allows communication among the participatinggroup members using the MSRP (1813). Thus, group ISC session, integratedthrough ISCConvergenceID, for the content viewing and the communicationis established for content identified by ContentRef.

Upon request from the ISC user A to pause the content that is beingviewed, the initiator ISC client sends (1814) RTSP PAUSE request towardsthe media function 401. The ISC user is also allowed to perform otherRTSP trick play commands such as FORWARD, REWIND, SKIP and the like.Upon receiving the request from the ISC user A to pause the content, themedia function stops (1815) delivering the content in the UDP/RTP tunnelto both the initiator ISC client 101 and the recipient ISC client 102.

Upon request from the ISC user A to resume the content that is beingpaused, the initiator ISC client sends (1816) RTSP RESUME requesttowards the media function 401. Upon receiving the request from the ISCuser A to resume the content, the media function 401 starts (1817)delivering the content to both the initiator ISC client 101 and therecipient ISC client 102 in the UDP/RTP tunnel from the position whereit was ‘paused’ by the ISC user A.

FIG. 19 illustrates the example sequence diagram for forming the ad-hocISC group to establish the group ISC session when contents available tothe ad-hoc group is unicast, according to embodiments as disclosedherein. The FIG. 19 depicts the initiator ISC client 101, the recipientISC client 102, the recipient ISC client 103, the ISC server 105including the media function 401 and the communication function 402 andthe ISC CPGateway 107 exchanging SIP messages for establishing thecontent viewing and the communication for the group ISC session. Thesequence of steps for establishing content viewing and the communicationbetween the group members are same as described in FIG. 14, except thead-hoc group instead of the pre-defined group. The ad-hoc groupdynamically formed by the ISC user A of the initiator ISC client 101does not have the pre-defined GroupID. Thus, the initiator ISC client101 sends the URI list to inform the ISC server 105 about the groupmembers. Hence, the media function 401 is not required to retrieve thegroup members and check the group policy from the ISC XDMS 106.

Except for the above changes the sequence of steps is similar to thesteps described in FIG. 14 as is not described in details to avidrepetition.

The media function 401 receives (1901) the desired contents of thecontent list from the content provider through the ISCCPGateway 107. Theinitiator ISC client 101 sends (1902) first SIP INVITE to the mediafunction 401 that includes the URI list of the group members of thead-hoc group. The media function 401 forwards (1903) the first SIPINVITE to the group members (recipient ISC client 102 and 103respectively) based on the received URI list. Further, the initiator ISCclient 101 uses the existing URI list used during generation of thefirst SIP INVITE and then sends (1904) the second SIP INVITE to thecommunication function 402. Further, the communication function 402forwards (1905) the second SIP INVITE to the group members (recipientISC client 102 and 103 respectively) based on the received URI list.

On reception (1906 and 1908) of 200 OK signal from the one or morerecipient ISC client by the media function 401, the media function 401sends (1907) 200 OK to the initiator ISC client 101. Thereafter, themedia function 401 delivers (1909) the contents requested by the ISCuser A of the initiator ISC client 101 in the UDP/RTP tunnel.

On reception (1910 and 1913) 200 OK from at least one of the recipientISC clients 102 and 103 respectively, the communication function 402sends (1911) 200 OK to the initiator ISC client 101. Further, thecommunication function 402 allows communication among the participatinggroup members using the MSRP (1912). Thus, group ISC session with thead-hoc group, integrated through ISCConvergenceID, for the contentviewing and the communication is established. The initiator ISC client101 can further change content and play controls as desired, as there isno group policy stored in the ISC XDMS for the ISC ad-hoc group.

FIG. 20 illustrates the example sequence diagram for extending theestablished one to one ISC session to the group ISC session, accordingto embodiments as disclosed herein. The FIG. 20 depicts the initiatorISC client 101, the recipient ISC client 102, the recipient ISC client103 and the ISC server 105 including the media function 401 and thecommunication function 402 exchanging SIP messages for the contentviewing and the communication for the group ISC session. Further, theFIG. 20 depicts the 1-1 ISC session for content viewing andcommunication between ISC users A and B after performing steps describedin FIG. 9 and FIG. 10. If ISC user A desires to add new ISC user C (therecipient ISC client 103) to the ongoing 1-1 session, then upon such arequest the initiator ISC client generates a SIP INVITE request forresending the SIP INVITE as specified in RFC 3261 with the followingclarifications as provided by the method disclosed:

1. Include Request-URI to the URI of the ISC Server provisioned in theclient.

2. Include the ISC feature tag CV_FT which is for initiating Groupcontent viewing and communication CV_FT with ICSI value(+g.3gpp.icsi-ref=“urn %3Aurn-7%3A3gpp-service.ims.icsi.omalsc.cv-cm) isincluded in Accept-Contact header field, Contact header field andP-Preferred-Service header field. And CV_FT with IARI value(+g.3gpp.icsi-ref=”urn%3Aurn-7%3A3gpp-service.imslari.omalsc.group-cv-cm) is included inAccept-Contact header field.

3. Include address of the recipient ISC client 102 and 103 respectively.The URI-List includes the URI-List in the body where the address ofrecipient ISC client additionally includes ‘Session-Replaces’ with theongoing 1-1 session identity.

Include the ContentRef and may be additional content informationcorresponding to the current content the established ISC group iswatching.

4. Include globally unique identifier (new value is generated if it isfor initiating new content viewing session otherwise from existingcontent viewing session) for determining the Content Viewing associatedto ISC Convergence in the ISCConvergence-ID.

5. Include the SDP for Unicast content viewing and below headers in thebody.

6. Include the ContentRef corresponding to the content the ISC user Ahas selected to watch. The value of this field is obtained from thecontents list. For example the value of ContentRef is included in theMIME SDP body of the SIP INVITE under new Content-Type header field“application/ISC-content-request+xml”.

Further, the initiator ISC client 101 resends (2001) the SIP INVITErequest for extending the one to one ISC session to the group ISCsession towards the media function 401. Upon receiving the SIP INVITErequest from the Client A with the URI list containing Session-Replacesheader for Client B, the media function 401 generates SIP INVITE requesttowards Client B including the information to replace the ongoing 1-1Session Identity.

Upon receiving the resent SIP INVITE request from the Client A with theURI List containing address of the recipient ISC client 103 to beincluded for content viewing, the media function 401 generates andforwards (2002) another SIP INVITE request towards recipient ISC client103. The initiator ISC client resends (2004) the SIP INVITE forcommunication to the communication function 402 with similar parametersas in the resent SIP invite, for content viewing, except the feature tagindicates CPM_FT for the communication.

After receiving (2007, 2009, 2010 and 2012) successful response 200 OKfor the SIP INVITE requests and ISC server 105 sends 200 OK (2008 and2011) to the initiator ISC client 101. Thus, the 1-1 content viewing andcommunication session between ISC user A and B respectively is nowdynamically extended to group ISC session with the new ad-hoc group forthe content viewing and communication among ISC users A, B and Crespectively.

FIG. 21 illustrates the example sequence diagram for establishing groupISC session for content viewing and communication when the mediafunction and the communication function are integrated in the ISCserver, according to embodiments as disclosed herein. The FIG. 21depicts the initiator ISC client 101, the recipient ISC client 102, therecipient ISC client 103, the ISC server 105 with integrated mediafunction and communication function and the ISCCPGateway 107 exchangingSIP messages for the content viewing and the communication for the groupISC session.

The media function 401 receives (2101) the content from the contentprovider through the ISC CPGateway 107. The sequence steps forestablishing the group ISC session for content viewing and communicationare similar to the steps as described in FIG. 13 with respect to one toone ISC session, except that the combined SIP INVITE sent (2102) to theISC server 105 includes the ISC GroupID to inform the ISC server 105forward the combined SIP INVITE to all the group members (recipients ISCclients within the group specified by ISC GroupID). Further, the ISCserver 105 retrieves the group members and the group policy from the ISCXDMS 106 and forwards (2103) the combined SIP INVITE to all invited thegroup members (recipient ISC client 102 and 103 respectively).

The invited group members respond (2104 and 2106) with 200 OK thatincludes SDP1: OK, SDP2: OK (combined SIP INVITE accept message) inresponse to the combined SIP INVITE, if there are no errors to therequest. The 200 OK received indicates that the group members acceptboth the content viewing and the communication invites with initiatorISC client 101. If error is identified, then the ISC server 105 respondswith error as specified in IETF RFC 3261. The ISC server 105 forwards(2105) the 200 OK to the initiator ISC client 101 on reception of the200 OK from either of the recipient ISC client.

The ISC server 105 starts (2107) delivering the content corresponding toContentRef in the UDP/RTP tunnel and allows communication among thegroup members. Now the group members watch the same content andcommunicate with each other integrated through ISCConvergenceID.

FIG. 22 illustrates the computing environment implementing the methodand system for establishing the ISC session for integrating contentviewing and communication, according to embodiments as disclosed herein.As depicted the computing environment 2201 comprises at least oneprocessing unit 2204 that is equipped with a control unit 2202 and anArithmetic Logic Unit (ALU) 2203, a memory 2205, a storage unit 2206,plurality of networking devices 2208 and a plurality of input output(I/O) devices 2207. The processing unit 2204 is responsible forprocessing the instructions of the algorithm. The processing unit 2204receives commands from the control unit in order to perform itsprocessing. Further, any logical and arithmetic operations involved inthe execution of the instructions are computed with the help of the ALU2203.

The overall computing environment 2201 can be composed of multiplehomogeneous and/or heterogeneous cores, multiple CPUs of differentkinds, special media and other accelerators. The processing unit 2204 isresponsible for processing the instructions of the algorithm. Further,the plurality of processing units 2204 may be located on a single chipor over multiple chips.

The algorithm comprising of instructions and codes required for theimplementation are stored in either the memory unit 2205 or the storage2206 or both. At the time of execution, the instructions may be fetchedfrom the corresponding memory 2205 and/or storage 2206, and executed bythe processing unit 2204.

In case of any hardware implementations various networking devices 2208or external I/O devices 2207 may be connected to the computingenvironment to support the implementation through the networking unitand the I/O device unit.

The embodiments disclosed herein can be implemented through at least onesoftware program running on at least one hardware device and performingnetwork management functions to control the elements. The elements shownin FIGS. 1, 3, 4, 6, through 22 include blocks which can be at least oneof a hardware device, or a combination of hardware device and softwaremodule.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the embodiments herein that others can, byapplying current knowledge, readily modify and/or adapt for variousapplications such specific embodiments without departing from thegeneric concept, and, therefore, such adaptations and modificationsshould and are intended to be comprehended within the meaning and rangeof equivalents of the disclosed embodiments. It is to be understood thatthe phraseology or terminology employed herein is for the purpose ofdescription and not of limitation. Therefore, while the embodimentsherein have been described in terms of preferred embodiments, thoseskilled in the art will recognize that the embodiments herein can bepracticed with modification within the spirit and scope of theembodiments as described herein.

1.-27. (canceled)
 28. A method for establishing an immersive socialcentre (ISC) session by an ISC server, wherein said method comprises:receiving a first session initiation protocol (SIP) invite requestincluding at least one first parameter from an originating ISC client bya media function in said ISC server for initiating said ISC session fora content viewing, wherein said at least one first parameter comprises aheader field, at least one element in a multipurpose internet mailextensions (MIME) body; receiving a second SIP invite request comprisingat least one second parameter from said originating ISC client by acommunication function in said ISC server to initiate said ISC sessionfor a communication, wherein said at least one second parametercomprises said header field and said at least one element in said MIMEbody; establishing said ISC session for said content viewing by saidmedia function based on said first SIP invite request; and establishingsaid ISC session for said communication by said communication functionbased on said second SIP invite request.
 29. The method of claim 28,wherein said header field in said first SIP invite request is said ISCconvergence ID indicating a globally unique identifier for SIP messagesassociated request and response for said ISC session for at least one ofsaid content viewing and said communication, and wherein SIP messagesassociated requests and responses for said ISC session for same contentviewing and same communication include the same value for the ISCconvergence ID.
 30. The method of claim 29, wherein headers in saidheader field in said first SIP invite request comprise at least one ofan Accept-Contact header, a Contact header and a P-Preferred-Serviceheader, wherein a IP multimedia subsystem (EMS) communication serviceidentifier (ICSI) included and an IMS application reference identifier(IARI) feature tag in said headers, and wherein said ICSI feature tagindicates whether said initiated ISC session is for invoking one of saidmedia function for said content viewing and said communication functionfor said communication, said IARI feature tag indicates a terminatingISC client among plurality of terminating ISC clients whether saidinitiated ISC session is one of a self ISC session, a one to one ISCsession, a group ISC session.
 31. The method of claim 28, wherein, saidat least one element in said MIME body comprises a ISC session type anda synchronization, wherein, said ISC session type indicates saidterminating ISC client whether said initiated ISC session is for atleast one of said content viewing and said communication, and saidsynchronization indicates said media function whether said originatingISC client and said terminating ISC client in said one to one ISCsession are synchronized for said content viewing, wherein said ISCsession type is used by said terminating ISC client to indicate thatsaid terminating ISC client is required to wait for said second SIPinvite request after receiving said first SIP invite request.
 32. Themethod of claim 28, wherein said at least one second parameter comprisesa communication session identifier assigned with a value of said ISCconvergence ID, and wherein said communication session identifier is aconverge IP messaging (CPM) conversation ID identifying saidcommunication.
 33. A method for initiating an immersive social centre(ISC) session by an originating ISC client, the method comprising:receiving a request to initiate said ISC session for at least one ofcontent viewing and communication; generating and transmitting a firstsession initiation protocol (SIP) invite request including at least onefirst parameter to a media function in a ISC server for initiating saidISC session for said content viewing, wherein said at least one firstparameter comprises an header field, and at least one element in amultipurpose internet mail extensions (MIME) body; generating andtransmitting a second SIP invite request comprising at least one secondparameter to a communication function in said ISC server to initiatesaid ISC session for said communication, wherein said at least onesecond parameter comprises said header field and said at least oneelement in said MIME body; participating in said ISC session for contentviewing after said media function establishes said ISC session; andparticipating in said ISC session for communication after saidcommunication function establishes said ISC session.
 34. The method ofclaim 33, wherein said header field in said first SIP invite request isISC convergence ID indicating a globally unique identifier for SIPmessages associated request and response for said ISC session for atleast one of said content viewing and said communication, and whereinSIP messages associated requests and responses for said ISC session forsame content viewing and same communication include the same value forthe ISC convergence ID.
 35. The method of claim 34, wherein headers insaid header field in said first SIP invite request comprise at least oneof an Accept-Contact header, a Contact header and a P-Preferred-Serviceheader, wherein a IP multimedia subsystem (IMS) communication serviceidentifier (ICSI) and an IMS application reference identifier (IARI)feature tag included in said headers, and wherein said ICSI feature tagindicates whether said initiated ISC session is for invoking one of saidmedia function for said content viewing and said communication functionfor said communication said content viewing and said communication, andsaid IARI feature tag indicates a terminating ISC client among pluralityof terminating ISC clients whether said initiated ISC session is one ofa self ISC session, a one to one ISC session, a group ISC session. 36.The method of claim 35, wherein said at least one element in said MIMEbody comprises a ISC session type and a synchronization, wherein saidISC session type indicates said terminating ISC client whether saidinitiated ISC session is for at least one of said content viewing andsaid communication, and said synchronization indicates said mediafunction whether said originating ISC client and a terminating ISCclient in said one to one ISC session are synchronized for said contentviewing, wherein said ISC session type is used by said terminating ISCclient to indicate that said terminating ISC client is required to waitfor said second SIP invite request after receiving said first SIP inviterequest.
 37. The method of claim 33, wherein said at least one secondparameter comprises a communication session identifier assigned with avalue of said ISC convergence ID, and wherein said communication sessionidentifier comprises a converge IP messaging (CPM) conversation IDidentifying said communication.
 38. A method for participating in animmersive social centre (ISC) session by an terminating ISC client, themethod comprising: receiving at least one of a first session initiationprotocol (SIP) invite request from a media function of a ISC server anda second SIP invite request from a communication function of said ISCserver for participating in an ISC session initiated by an originatingISC client; determining whether said ISC session is for at least one ofsaid content viewing and said communication based on a value of an ISCsessiontype in at least one of the first SIP invite request and thesecond SIP invite request; and sending response to said media functionand said communication function indicating participation in said ISCsession based on input from a ISC user of said terminating ISC client.39. The method of claim 38, wherein said first SIP invite requestcomprises a header field including an ISC convergence ID and an ISCfeature tag, wherein said ISC convergence ID comprises a globally uniqueidentifier for SIP messages associated request and response for said ISCsession for at least one of said content viewing and said communication,and wherein SIP messages associated requests and responses for said ISCsession for same content viewing and same communication include the samevalue for the ISC convergence ID.
 40. The method of claim 38, whereinsaid first SIP invite request further comprises at least one element ina MIME body, and wherein the ISC session type indicates whether said ISCsession is for at least one of said content viewing, and saidcommunication.
 41. The method of claim 38, wherein said second SIPinvite request comprises a communication session identifier assignedwith a value of said ISC convergence ID, and wherein said communicationsession identifier comprises a converge IP messaging (CPM) conversationID identifying said communication.
 42. An apparatus for establishing animmersive social centre (ISC) session, the apparatus comprising: a mediafunction configured to: receive a first session initiation protocol(SIP) invite request including at least one first parameter from anoriginating ISC client for initiating said ISC session for a contentviewing, wherein said at least one first parameter comprises a headerfield, at least one element in a multipurpose internet mail extensions(MIME) body, and establish said ISC session for said content viewingbased on said first SIP invite request; and a communication functionconfigured to: receive a second SIP invite request comprising at leastone second parameter from said originating ISC client to initiate saidISC session for a communication, wherein said at least one secondparameter comprises said header field and said at least one element insaid MIME body, and establish said ISC session for said communicationbased on said second SIP invite request.
 43. The apparatus of claim 42,wherein said header field in said first SIP invite request comprises anISC convergence ID indicating a globally unique identifier for SIPmessages associated request and response for said ISC session for atleast one of said content viewing and said communication, wherein, saidat least one element in said MIME body comprises a ISC session type anda synchronization, and wherein said ISC session type indicates saidterminating ISC client whether said initiated ISC session is for atleast one of said content viewing and said communication, and saidsynchronization indicates said media function whether said originatingISC client and a terminating ISC client in said one to one ISC sessionare synchronized for said content viewing.
 44. An apparatus forinitiating an immersive social centre (ISC) session, the apparatuscomprising: an ISC client configured to: receive a request to initiatesaid ISC session for at least one of content viewing and communication,generate and transmit a first session initiation protocol (SIP) inviterequest including at least one first parameter to a media function in aISC server for initiating said ISC session for said content viewing,wherein said at least one first parameter comprises an header field, andat least one element in a multipurpose internet mail extensions (MIME)body, generate and transmit a second SIP invite request comprising atleast one second parameter to a communication function in said ISCserver to initiate said ISC session for said communication, wherein saidat least one second parameter comprises said header field and said atleast one element in said MIME body, participate in said ISC session forcontent viewing after said media function establishes said ISC session,and participate in said ISC session for communication after saidcommunication function establishes said ISC session.
 45. The apparatusof claim 44, wherein said header field in said first SIP invite requestcomprises an ISC convergence ID indicating a globally unique identifierfor SIP messages associated request and response for said ISC sessionfor at least one of said content viewing and said communication,wherein, said at least one element in said MIME body comprises a ISCsession type and a synchronization, and wherein said ISC session typeindicates said terminating ISC client whether said initiated ISC sessionis for at least one of said content viewing and said communication, andsaid synchronization indicates said media function whether saidoriginating ISC client and a terminating ISC client in said one to oneISC session are synchronized for said content viewing.
 46. An apparatusfor participating in an immersive social centre (ISC) session, theapparatus comprising: an ISC client configured to: receive at least oneof a first session initiation protocol (SIP) invite request from a mediafunction of a ISC server and a second SIP invite request from acommunication function of said ISC server for participating in an ISCsession initiated by an originating ISC client, determine whether saidISC session is for at least one of said content viewing and saidcommunication based on a value of an ISC session type in at least one ofthe first SIP invite request and the second SIP invite request, andtransmit a response to said media function and said communicationfunction indicating participation in said ISC session based on inputfrom an ISC user of said terminating ISC client.
 47. The apparatus ofclaim 46, wherein said first SIP invite request comprises a header fieldincluding an ISC convergence ID and an ISC feature tag, wherein said ISCconvergence ID comprises a globally unique identifier for SIP messagesassociated request and response for said ISC session for at least one ofsaid content viewing and said communication, wherein said first SIPinvite request further comprises at least one element in a MIME body,and wherein the ISC session type indicates whether said ISC session isfor at least one of said content viewing, and said communication.